Server ProvisionerApplication · Cisco

CVE-2013-3407

MEDIUM · 5.0 CVSS v2.0 Published 2013-11-18
Fix available
A fix is available. Upgrade to after 6.4.0 or later.
See remediation →
59/100
Remediation priority · Elevated
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 web interface in Cisco Server Provisioner 6.4.0 Patch 5-1301292331 and earlier does not require authentication for unspecified pages, which allows remote attackers to obtain sensitive information via a direct request, aka Bug ID CSCug65664.

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 confidence

The Cisco Server Provisioner web interface versions 6.4.0 Patch 5-1301292331 and earlier contains an authentication bypass vulnerability where certain pages do not require authentication, allowing remote unauthenticated attackers to directly request these pages and obtain sensitive information.

MitigationApply the vendor patch from Cisco for CSCug65664. If a patch is unavailable, restrict network access to the Cisco Server Provisioner web interface using firewall rules or ACLs to prevent unauthorized external access.

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
Server ProvisionerApplication
Affected:<= 6.4.0= 6.3.0= 6.4.0

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
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 checks

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

  1. Identify the installed Cisco Server Provisioner version
    Access the web interface admin page or check the system configuration file for the version number. Look for a version string indicating 6.4.0 Patch 5-1301292331 or earlier, or versions 6.3.0 or 6.4.0.
    Affected if The installed version is 6.4.0 Patch 5-1301292331 or any earlier version, or specifically 6.3.0 or 6.4.0.
  2. Confirm the web interface is accessible
    Attempt to reach the Cisco Server Provisioner web interface from a network location. Verify that HTTP or HTTPS responses are received from the server.
    Affected if The web interface responds to requests, indicating it is running and reachable.
  3. Test for unauthenticated access to sensitive pages
    Send direct HTTP requests to common web interface paths without providing any authentication credentials. Observe whether the server returns sensitive information or allows access to administrative functions.
    Affected if The server returns sensitive data or allows access to restricted pages without requiring login credentials.
  4. Review network exposure of the web interface
    Check firewall rules, ACLs, or network configurations to determine if the Cisco Server Provisioner web interface is accessible from untrusted networks or the internet.
    Affected if The web interface is exposed to untrusted networks without network-level access controls.

A user is affected if the Cisco Server Provisioner version is 6.4.0 Patch 5-1301292331 or earlier (including 6.3.0 and 6.4.0) AND the web interface is accessible without authentication to unauthorized users.

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 6.4.0
Interim mitigation

Apply the vendor patch from Cisco for CSCug65664. If a patch is unavailable, restrict network access to the Cisco Server Provisioner web interface using firewall rules or ACLs to prevent unauthorized external access.

Fix this in Server Provisioner Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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