Cache EngineHardware / appliance · Cisco
CVE-1999-1000
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 administration interface for Cisco Cache Engine allows remote attackers to view performance statistics.
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 · moderate confidenceThe Cisco Cache Engine web administration interface contains an information disclosure vulnerability allowing unauthenticated remote attackers to view performance statistics. This appears to be a missing access control or authentication bypass in the web-based admin functionality.
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
Cache EngineHardware / appliance
= 2CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Cisco Cache Engine installationDetermine if Cisco Cache Engine version 2 is running on the system. Check for the product via system inventory, running services, or network scanning for Cisco Cache Engine signatures.Affected if The system is running Cisco Cache Engine version 2.
-
Locate the web administration interfaceCheck if the web-based admin interface is active. Common ports for Cisco web interfaces include 80, 8080, or 8000. Attempt to access the admin URL or look for Cisco Cache Engine web service responses.Affected if The web administration interface is accessible on the network.
-
Test unauthenticated access to performance statisticsAccess the performance statistics or status pages (such as /stats, /performance, or similar admin endpoints) without providing any credentials. Observe whether the page loads and displays statistical data.Affected if Performance statistics are displayed without requiring authentication.
-
Verify authentication requirement on admin endpointsCompare the behavior of accessing admin pages with and without credentials. Check if the web interface enforces login before revealing any administrative or statistical data.Affected if Admin and statistics pages are accessible without any authentication credentials.
A user is affected if Cisco Cache Engine version 2 is running with its web administration interface exposed and performance statistics are visible without authentication.
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 dataRestrict access to the web administration interface to authorized internal networks only, implement strong authentication for admin interfaces, and consider upgrading to a supported solution as Cisco Cache Engine products from this era are likely End of Life.
Fix this in Cache Engine
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-1999-1000 — 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-1999-1000 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