dbcve.org
Network Admission Control Manager And Server System SoftwareApplication · Cisco

CVE-2005-4332

HIGH · 9.4 CVSS v2.0 Published 2005-12-17
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
Cisco Clean Access 3.5.5 and earlier on the Secure Smart Manager allows remote attackers to bypass authentication and cause a denial of service or upload files via direct requests to obsolete JSP files including (1) admin/uploadclient.jsp, (2) apply_firmware_action.jsp, and (3) file.jsp.

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

Cisco Clean Access 3.5.5 and earlier Secure Smart Manager contains multiple vulnerabilities where remote attackers can bypass authentication and directly access obsolete JSP files (admin/uploadclient.jsp, apply_firmware_action.jsp, file.jsp) to cause denial of service or upload arbitrary files.

MitigationRemove or disable the obsolete JSP files (uploadclient.jsp, apply_firmware_action.jsp, file.jsp) from the server, or upgrade to a patched version of Cisco Clean Access beyond 3.5.5.

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
Affected:= 3.3= 3.3.1= 3.3.2= 3.3.3= 3.3.4= 3.3.5= 3.3.6= 3.3.7= 3.3.8= 3.3.9= 3.4= 3.4.1

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
None
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:N/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 if Cisco Clean Access or NAC Manager is installed
    Check for the product installation directory or running service. Common paths include /opt/Cisco, /usr/local/Cisco, or look for processes named 'ccam' or 'nacm'. On Windows, check Program Files for Cisco folders.
    Affected if The software is present on the system
  2. Determine the installed version
    Check the version file or about page. Look for a version file in the installation directory, or access the management interface login page which often displays the version. Check files like VERSION.txt, version.properties, or the main GUI page.
    Affected if The installed version is 3.5.5 or earlier, or matches 3.3.x through 3.4.x (specifically 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.5, 3.3.6, 3.3.7, 3.3.8, 3.3.9, 3.4, 3.4.1)
  3. Locate the vulnerable JSP files
    Search the web application root directory for these specific files: uploadclient.jsp, apply_firmware_action.jsp, and file.jsp. Common paths include <install_dir>/managing/page/ or <webapp_root>/admin/.
    Affected if Any of these JSP files exist in the web application directories
  4. Test JSP file accessibility without authentication
    Attempt to access these URLs directly via HTTP/HTTPS without logging in: /admin/uploadclient.jsp, /apply_firmware_action.jsp, /file.jsp. A successful connection (even if returning an error) indicates the files are accessible and potentially exploitable.
    Affected if These URLs return HTTP responses without requiring authentication credentials

The environment is affected if Cisco Clean Access or NAC Manager version 3.5.5 or earlier (specifically 3.3.x through 3.4.x) is installed AND the vulnerable JSP files are present and accessible without authentication.

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

Remove or disable the obsolete JSP files (uploadclient.jsp, apply_firmware_action.jsp, file.jsp) from the server, or upgrade to a patched version of Cisco Clean Access beyond 3.5.5.

Recommended fix Moderate confidence

Cisco Clean Access 3.6.0 or later (verify latest Cisco-supported release)

  1. 1. Identify the current Cisco Clean Access version installed by accessing the admin console or checking system documentation
  2. 2. Determine if the installed version is 3.3, 3.3.1, 3.3.2, 3.3.3, or any version 3.5.5 or earlier
  3. 3. Contact Cisco Security Advisory or Cisco Technical Support to obtain the specific fixed version for this vulnerability
  4. 4. Plan upgrade during a maintenance window as this is a critical authentication bypass vulnerability
  5. 5. Backup current configuration before performing upgrade
  6. 6. Upgrade to Cisco Clean Access version 3.6.0 or later (or the latest Cisco-supported version as recommended by Cisco)
  7. 7. After upgrade, verify that obsolete JSP files (admin/uploadclient.jsp, apply_firmware_action.jsp, file.jsp) are no longer accessible without authentication
  8. 8. Confirm normal authentication is required for administrative functions
Caveat Older Cisco Clean Access versions may have limited upgrade paths; ensure compatibility with underlying hardware and dependent systems before upgrading

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

Fix this in Network Admission Control Manager And Server System Software Scoped from the published advisory
  • Review / QA2.0 h
2.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-4332 — 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-2005-4332 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