dbcve.org
Application Control Engine Device ManagerApplication · Cisco

CVE-2009-0615

HIGH · 9.0 CVSS v2.0 Published 2009-02-26
Fix available
A fix is available. Upgrade to after 1.2 or later.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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
Directory traversal vulnerability in Cisco Application Networking Manager (ANM) before 2.0 and Application Control Engine (ACE) Device Manager before A3(2.1) allows remote authenticated users to read or modify arbitrary files via unspecified vectors, related to "invalid directory permissions."

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

Directory traversal vulnerability in Cisco Application Networking Manager (ANM) and Application Control Engine (ACE) Device Manager allows remote authenticated users to read or modify arbitrary files on the system due to invalid directory permissions. The CVSS score of 9 indicates severe impact from this flaw affecting versions prior to ANM 2.0 and ACE Device Manager A3(2.1).

MitigationUpgrade to Cisco ANM 2.0 or later and ACE Device Manager A3(2.1) or later to remediate the invalid directory permissions that allow arbitrary file 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
Application Control Engine Device ManagerApplication
Affected:<= 1.2= 1.1
Application Networking ManagerApplication
Affected:<= 1.2= 1.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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/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 installed Cisco management product
    Locate Cisco Application Networking Manager (ANM) or ACE Device Manager software on the system. Check for process names such as 'anm' or 'acedm' or look for installation directories containing 'Cisco ANM' or 'ACE Device Manager' in the program files or application directories.
    Affected if Neither Cisco ANM nor ACE Device Manager is installed on the system.
  2. Determine product version
    Access the web-based management interface and navigate to the About or version information page, or check the installed software version via the command line if available. Common paths include the login page or help/about section of the ANM or ACE Device Manager web interface.
    Affected if The version cannot be determined or the product is not found.
  3. Compare version to affected ranges
    Verify if the installed version matches or precedes the affected versions: Cisco ACE Device Manager versions 1.1, 1.2 and earlier; Cisco Application Networking Manager versions 1.1, 1.2 and earlier.
    Affected if The installed version is 1.1 or 1.2 or any version prior to 2.0 for ANM, or prior to A3(2.1) for ACE Device Manager.
  4. Confirm web management interface accessibility
    Determine if the ANM or ACE Device Manager web interface is exposed and accessible on the network. Check firewall rules, listening ports (typically 443, 8443, or 8080 for management interfaces), and network exposure settings.
    Affected if The web management interface is accessible from the network and the product version falls within the affected range.

A user is affected if Cisco ANM version 1.2 or earlier (including 1.1) or ACE Device Manager version 1.2 or earlier (including 1.1) is installed and the web management interface is network-accessible.

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
Upgrade available Upgrade to a release after 1.2
Interim mitigation

Upgrade to Cisco ANM 2.0 or later and ACE Device Manager A3(2.1) or later to remediate the invalid directory permissions that allow arbitrary file access.

Recommended fix High confidence

Application Networking Manager 2.0+ and ACE Device Manager A3(2.1)+

  1. 1. Identify whether you are running Application Networking Manager (ANM) or ACE Device Manager.
  2. 2. For ANM users: Upgrade to version 2.0 or later.
  3. 3. For ACE Device Manager users: Upgrade to version A3(2.1) or later.
  4. 4. After upgrading, verify the directory permissions have been corrected by reviewing the release notes or consulting Cisco documentation.
  5. 5. Test that authenticated users can no longer traverse directories outside their intended scope.
Caveat Review Cisco release notes for ANM 2.0 and ACE Device Manager A3(2.1) for any configuration or compatibility changes before upgrading.

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

Fix this in Application Control Engine Device Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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