dbcve.org
Rvs4000Hardware / appliance · Cisco

CVE-2011-1645

HIGH · 9.3 CVSS v2.0 Published 2011-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The web management interface on the Cisco RVS4000 Gigabit Security Router with software 1.x before 1.3.3.4 and 2.x before 2.0.2.7, and the WRVS4400N Gigabit Security Router with software before 2.0.2.1, allows remote attackers to read the backup configuration file, and consequently execute arbitrary code, via unspecified vectors, aka Bug ID CSCtn23871.

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 confidence

The web management interface on Cisco RVS4000 and WRVS4400N Gigabit Security Routers contains an unauthenticated arbitrary file read vulnerability that allows remote attackers to obtain backup configuration files. These backup configs contain sensitive credentials that can be leveraged to execute arbitrary code on the device, resulting in full compromise.

MitigationApply the vendor-supplied patches: upgrade RVS4000 to software 1.3.3.4 (or later 1.x) / 2.0.2.7 (or later 2.x), and WRVS4400N to 2.0.2.1 or later. If patching is impossible, disable the web management interface remotely or restrict management access to trusted IP addresses via firewall rules.

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
Rvs4000Hardware / appliance
Affected:= 1= 2
Rvs4000 SoftwareApplication
Affected:= 1.3.0.5= 1.3.1.0= 1.3.2.0= 2.0.0.3
Wrvs4400nHardware / appliance
Affected:= 1.0= 1.1= 2
Wrvs4400n SoftwareApplication
Affected:= 1.3.0.5= 1.3.1.0= 1.3.2.0= 2.0.0.3

CVSS 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the router web interface or check the device label to confirm the model is Cisco RVS4000 or WRVS4400N
    Affected if Device model is not RVS4000 or WRVS4400N, then not affected by this specific CVE
  2. Check the firmware version
    Log into the router web interface and navigate to the Status or Administration section to view the software version, or use the command line and run 'show version'
    Affected if The running firmware version is 1.3.0.5, 1.3.1.0, 1.3.2.0, or 2.0.0.3 - compare your installed version to the affected ranges provided
  3. Verify web management interface is enabled
    Check the router configuration under Administration or Management settings to see if the HTTP/HTTPS web management interface is enabled
    Affected if The web management interface is enabled and accessible from the network segment being tested
  4. Confirm the vulnerable endpoint responds
    Send an HTTP GET request to the backup configuration file path (commonly /backup.cfg or similar). For RVS4000/WRVS4400N, attempt to access the configuration export function without authentication.
    Affected if The device returns a configuration file without requiring authentication, indicating the file read vulnerability is present

You are affected if you have a Cisco RVS4000 or WRVS4400N router running software versions 1.3.0.5, 1.3.1.0, 1.3.2.0, or 2.0.0.3 with the web management interface enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches: upgrade RVS4000 to software 1.3.3.4 (or later 1.x) / 2.0.2.7 (or later 2.x), and WRVS4400N to 2.0.2.1 or later. If patching is impossible, disable the web management interface remotely or restrict management access to trusted IP addresses via firewall rules.

Recommended fix High confidence

RVS4000 1.x: upgrade to 1.3.3.4 or later; RVS4000 2.x: upgrade to 2.0.2.7 or later; WRVS4400N: upgrade to 2.0.2.1 or later

  1. Identify the current firmware version of the Cisco RVS4000 or WRVS4400N device
  2. Access the router's web management interface
  3. Navigate to the Administration or System section
  4. Locate the firmware upgrade option
  5. Upload and apply the appropriate fixed firmware version for your device model and current firmware branch
  6. After upgrade, verify the new firmware version is installed
  7. Change default administrative credentials as the backup config may have been exposed
Caveat Firmware upgrades may temporarily interrupt network connectivity and should be performed during maintenance windows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rvs4000 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-1645 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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