Network Admission Control Manager And Server System SoftwareApplication · Cisco
CVE-2007-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 · uneditedCisco Clean Access (CCA) 3.5.x through 3.5.9 and 3.6.x through 3.6.1.1 on the Clean Access Manager (CAM) allows remote attackers to bypass authentication and download arbitrary manual database backups by guessing the snapshot filename using brute force, then making a direct request for the file.
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 confidenceCisco Clean Access Manager (CAM) versions 3.5.x through 3.5.9 and 3.6.x through 3.6.1.1 contains an authentication bypass vulnerability where remote attackers can download arbitrary manual database backups by brute-forcing snapshot filenames and making direct requests, bypassing the authentication mechanism entirely.
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
Network Admission Control Manager And Server System SoftwareApplication
>= 3.5.0, <= 3.5.9>= 3.6.0.0, <= 3.6.1.1CVSS 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
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/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.
-
Check installed CAM versionAccess the Cisco Clean Access Manager admin interface and navigate to the About or System Information page to view the software version, or run 'show version' via CLI if availableAffected if The installed version is 3.5.0 through 3.5.9 or 3.6.0.0 through 3.6.1.1
-
Identify backup file storage locationLocate the directory where manual database backup snapshots are stored on the CAM server filesystem. Check CAM configuration files or documentation for the default backup path.Affected if Manual database backup files exist and are stored in a web-accessible directory
-
Verify backup directory authentication requirementAttempt to access the backup directory or a known backup file via HTTP/HTTPS without providing valid credentials. Check if the server returns the file directly or rejects the request with an authentication challenge.Affected if Backup files are served without requiring authentication (HTTP 200 response with file content rather than HTTP 401/403 redirect to login)
-
Review access logs for backup file requestsExamine CAM web server access logs for suspicious requests to backup file paths, especially repeated requests with varying filenames that could indicate brute-force scanning activity.Affected if Logs show unauthenticated requests to backup file paths or patterns suggesting filename enumeration
A system is affected if it runs Cisco Clean Access Manager versions 3.5.0-3.5.9 or 3.6.0.0-3.6.1.1 AND has manual database backups accessible without authentication via direct HTTP requests.
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 dataUpgrade to a patched version of Cisco Clean Access that addresses this vulnerability, or implement additional access controls on the backup file directory and implement stronger filename randomization to prevent brute-force attacks.
Fix this in Network Admission Control Manager And Server System Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-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-2007-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