Broadband Operating SystemOperating system · Cisco
CVE-2001-0058
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 · uneditedThe Web interface to Cisco 600 routers running CBOS 2.4.1 and earlier allow remote attackers to cause a denial of service via a URL that does not end in a space character.
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 confidenceThe Cisco 600 router web interface contains a denial of service vulnerability where malformed HTTP requests (URLs not ending in a space character) cause the device to become unresponsive. This affects CBOS version 2.4.1 and earlier.
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
Broadband Operating SystemOperating system
<= 2.4.1
Cisco 6xx RoutersHardware / appliance
all versionsCVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 router modelCheck the physical device label or log into the device and run 'show version' to confirm the model is Cisco 600, 601, 602, 605, or 627/647/657 seriesAffected if The device is any Cisco 600 series router (all versions affected)
-
Determine the CBOS versionLog into the router CLI and run 'show version' or 'show system' to identify the CBOS firmware versionAffected if CBOS version is 2.4.1 or earlier (versions 2.4.1 and below are affected)
-
Verify the web interface is enabledCheck the router configuration by running 'show running-config' or 'show configuration' and look for 'ip http server' or similar HTTP service entriesAffected if The HTTP web server is enabled (the vulnerability requires the web interface to be active)
-
Confirm HTTP access is permittedAttempt to reach the router over HTTP port 80 from an authorized management network, or check ACLs that permit HTTP access to the deviceAffected if The router is accessible via HTTP (exposure to network makes exploitation possible)
You are affected if you have a Cisco 600 series router running CBOS version 2.4.1 or earlier with the web interface (HTTP server) enabled and accessible on your network.
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 dataReplace or upgrade the legacy Cisco 600 routers as CBOS is end-of-life and no patches are available. Consider network segmentation to isolate these devices if immediate replacement is not feasible.
Fix this in Broadband Operating System
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0058 — 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-2001-0058 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