Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2022-20705 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.4% 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-2 (Flaw Remediation) — 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-20705 encompasses multiple vulnerabilities, primarily stack-based buffer overflows tracked under CWE-121 and CWE-787, affecting Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers. These flaws carry a CVSS 3.1 score of 10.0 and can result in arbitrary code execution, privilege elevation, command execution, authentication bypass, execution of unsigned software, or denial of service.
Remote attackers can exploit the issues over the network without authentication or user interaction, leveraging the routers' exposed management interfaces to achieve full device compromise or service disruption.
The Cisco Security Advisory at tools.cisco.com provides official guidance and patches for the affected RV series models, while additional technical details appear in Zero Day Initiative advisories ZDI-22-409, ZDI-22-410, and ZDI-22-415 along with public exploit references on Packet Storm.
The associated EPSS score remains elevated, with a current value of 0.8021 and a recorded peak of 0.8186.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-25955
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 requires timely application of vendor patches that remediate the stack-based buffer overflows and related flaws described in the Cisco advisory.
Enforces boundary protection and interface restrictions that prevent unauthenticated remote attackers from reaching the exposed management services exploited by CVE-2022-20705.
Requires enforcement of access-control policies on device interfaces, limiting the ability of unauthenticated actors to reach vulnerable management functions even when the device is reachable.
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.