Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2022-20707 is a critical-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Cisco Rv340 Firmware. Its CVSS base score is 10.0 (Critical).
Operationally, ranked in the top 0.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SC-7 (Boundary Protection) and SI-10 (Information Input Validation) — 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.
CVE-2022-20707 covers multiple vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers. The issues are tracked under CWEs 121 and 787 and received a CVSS 3.1 score of 10.0, reflecting the potential for arbitrary code execution, privilege elevation, command execution, authentication bypass, execution of unsigned software, and denial of service.
An unauthenticated attacker with network access can trigger the flaws without user interaction or credentials, enabling full compromise of affected routers or service disruption. Public references include exploit code for authentication bypass and command injection as well as separate Zero Day Initiative reports confirming the same attack surface.
The primary Cisco Security Advisory supplies remediation guidance and is linked alongside the related ZDI entries. The associated EPSS score reached 0.8140 at peak and remains at that level, indicating sustained exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-25957
Vulnerability Data
Multiple vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers could allow an attacker to do any of the following: Execute arbitrary code Elevate privileges Execute arbitrary commands Bypass authentication and authorization protections Fetch and run unsigned…
more
software Cause denial of service (DoS) For more information about these vulnerabilities, see the Details section of this advisory.
- 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
Directly mitigates the stack-based buffer overflows and out-of-bounds writes (CWE-121/787) that enable unauthenticated code execution and command injection on the routers.
Enforces boundary protections on network-accessible routers to restrict the unauthenticated remote attack surface that leads to full device compromise or DoS.
Requires timely application of vendor patches that remediate the multiple high-severity flaws allowing arbitrary code execution and authentication bypass.
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.