CVE-2024-20381
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability in the JSON-RPC API feature in Cisco Crosswork Network Services Orchestrator (NSO) and ConfD that is used by the web-based management interfaces of Cisco Optical Site Manager and Cisco RV340 Dual WAN Gigabit VPN Routers could allow an authenticated, remote attacker to modify the configuration of an affected application or device. This vulnerability is due to improper authorization checks on the API. An attacker with privileges sufficient to access the affected application or device could exploit this vulnerability by sending malicious requests to the JSON-RPC API. A successful exploit could allow the attacker to make unauthorized modifications to the configuration of the affected application or device, including creating new user accounts or elevating their own privileges on an affected system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an authorization bypass vulnerability in the JSON-RPC API of Cisco Crosswork NSO and ConfD, affecting Cisco Optical Site Manager and RV340 routers. Due to improper authorization checks, an authenticated attacker can send malicious JSON-RPC requests to make unauthorized configuration changes, including creating new user accounts or escalating privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.5.1= 6.5.2= 6.5.3= 6.5.15= 6.5.25= 6.5.26= 6.5.28= 6.5.29= 6.5.31= 6.5.32= 6.5.33= 6.5.90= 4.4.1= 4.5.1= 4.7.1= 4.7.3= 5.1.1.1= 5.1.1.3= 5.1.2= 5.1.4.3= 5.2.0.3= 5.2.0.4= 5.2.1= 5.2.1.1= 1.0.00.29= 1.0.00.33= 1.0.01.16= 1.0.01.17= 1.0.01.18= 1.0.01.20= 1.0.02.16= 1.0.03.15= 1.0.03.16= 1.0.03.17= 1.0.03.18= 1.0.03.19CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed product and firmware versionFor Cisco IOS XR: run 'show version' on the CLI. For Cisco NSO: run 'ncs --version' or check the package metadata. For Small Business RV routers: access the web management interface and navigate to Administration > Firmware Upgrade or check the status page.Affected if The installed version matches one of the listed affected versions for the respective product.
-
Confirm web-based management interface is enabledCheck the device configuration or administration settings to determine if the HTTP/HTTPS web management interface is active. For IOS XR: look for 'http server' or 'xml agent' configuration. For NSO: verify the ConfD web UI or NETCONF/XML agent is running. For RV routers: check if remote management is enabled in the administration settings.Affected if The web-based management interface or JSON-RPC API is accessible and enabled.
-
Review user accounts for unauthorized administrative accountsAudit the local user database or directory integration for any newly created accounts with administrative or privilege-15 level access that were not created by authorized administrators. For IOS XR: run 'show users'. For RV routers: check the User Management page in the web interface.Affected if Unexpected or unauthorized accounts with elevated privileges exist in the system.
-
Audit configuration change logs for authorization bypass indicatorsReview system logs, audit logs, or configuration change history for operations performed by standard users that resulted in configuration modifications such as user account creation, privilege changes, or access control list alterations.Affected if Standard-privilege accounts have performed actions that should require higher authorization levels.
Your environment is affected if you are running any of the listed versions of Cisco IOS XR, Cisco Network Services Orchestrator, or Small Business RV Series Router Firmware with the web-based management or JSON-RPC interface enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Cisco's official patches for Crosswork NSO, ConfD, and the affected router/firewall products. Until patches are available, restrict API access to trusted administrative IPs only and monitor for unauthorized configuration changes.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20381 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20381 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data