CVE-2023-44386
Vapor 4.83.2 – 4.84.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2023-44386 is a medium-severity Improper Handling of Extra Values (CWE-231) vulnerability in Vapor Vapor. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-2631
Vulnerability Data
Vapor is an HTTP web framework for Swift. There is a denial of service vulnerability impacting all users of affected versions of Vapor. The HTTP1 error handler closed connections when HTTP parse errors occur instead of passing them on. The…
more
issue is fixed as of Vapor release 4.84.2.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require robust input validation that prevents improper handling of extra values.
Runtime monitoring of software can detect assertion-triggered crashes as adverse events.
Vulnerability identification processes can discover and record reachable-assertion flaws before deployment.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect extra-value handling issues but does not prevent them by itself.
Secure development lifecycle includes input validation and parameter handling that can prevent extra-value processing flaws.
Application security requirements typically mandate strict input validation and parameter count checks.
Secure architecture principles encourage robust input handling but do not specifically address extra-value scenarios.
Secure coding standards directly require validation of the exact number and type of input parameters.
Change management may catch order-related issues during reviews but does not address root cause.