Cisco 7xx RoutersHardware / appliance · Cisco

CVE-1999-0415

HIGH · 7.5 CVSS v2.0 Published 1999-03-11
Fix available
A fix is available. Upgrade to after 4.2 or later.
See remediation →
84/100
Remediation priority · High
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 HTTP server in Cisco 7xx series routers 3.2 through 4.2 is enabled by default, which allows remote attackers to change the router's configuration.

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 Cisco 7xx series routers (versions 3.2-4.2) have an HTTP server enabled by default, which allows unauthenticated remote attackers to access the router's web management interface and modify its configuration without any credentials.

MitigationDisable the HTTP server on affected Cisco 7xx routers via CLI configuration, or if these legacy devices are still in use, upgrade to a supported router version that disables HTTP by default. Given the age of these devices (1999 era), retirement and replacement is the recommended approach.

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
Cisco 7xx RoutersHardware / appliance
Affected:<= 4.2= 3.2

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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/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 checks

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

  1. Identify the router model
    Run 'show version' or check the physical device label to confirm it is a Cisco 7xx series router (such as 770, 771, 772, 775, 776, or similar)
    Affected if The device is a Cisco 7xx series router
  2. Check the IOS version
    Run 'show version' and look for the IOS version number in the output
    Affected if The IOS version is 3.2, 4.0, 4.1, or 4.2 (any version from 3.2 through 4.2)
  3. Verify HTTP server status
    Run 'show running-config | include ip http' or 'show ip http server status' to check if the HTTP server is enabled on the router
    Affected if HTTP server is enabled (the configuration shows 'ip http server' or similar indicating HTTP is active)

You are affected if you have a Cisco 7xx router running IOS version 3.2 through 4.2 with the HTTP server enabled, as this allows unauthenticated remote access to the management interface.

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.

From vendor data
Upgrade available Upgrade to a release after 4.2
Interim mitigation

Disable the HTTP server on affected Cisco 7xx routers via CLI configuration, or if these legacy devices are still in use, upgrade to a supported router version that disables HTTP by default. Given the age of these devices (1999 era), retirement and replacement is the recommended approach.

Fix this in Cisco 7xx Routers Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-1999-0415 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-1999-0415 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