Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-22274 is a critical-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Sonicwall Sonicos. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-16 (Memory Protection) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A stack-based buffer overflow vulnerability exists in SonicOS, the operating system used by SonicWall firewalls. The flaw is triggered by specially crafted HTTP requests and is tracked under CWE-121 and CWE-787. It received a CVSS v3.1 score of 9.8 and was publicly disclosed on 25 March 2022.
A remote unauthenticated attacker can exploit the issue over the network by sending malicious HTTP requests, leading to denial of service or potential remote code execution on the firewall. The SonicWall PSIRT advisory SNWLID-2022-0003 at https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0003 addresses the vulnerability. The associated EPSS score reached a peak of 0.5728 and currently stands at 0.4861.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-27421
Vulnerability Data
A Stack-based buffer overflow vulnerability in the SonicOS via HTTP request allows a remote unauthenticated attacker to cause Denial of Service (DoS) or potentially results in code execution in the firewall.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Enforces validation of all HTTP request inputs before processing, directly blocking the malformed payloads that trigger the stack buffer overflow.
Requires memory-protection mechanisms (e.g., ASLR, NX) that make successful exploitation of the stack-based overflow and resulting code execution far more difficult.
Restricts remote HTTP access to the firewall’s management interface to trusted endpoints and authenticated sessions, reducing the attack surface for unauthenticated exploitation.
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-development practices directly prevent introduction of stack buffer overflows.
Vulnerability scanning can discover stack buffer overflows but does not prevent their introduction.
Patching eliminates known instances of the weakness after discovery.
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 (fuzzing, static analysis) detects stack overflows before release.
Secure SDLC mandates buffer-safety practices that directly prevent stack overflows.
Application security requirements can specify buffer-size and input-validation rules.
Secure architecture principles include memory-safety and least-privilege stack usage.
Secure coding standards explicitly forbid unsafe buffer handling that causes CWE-121.
Change management can enforce review gates that catch unsafe memory operations before deployment.