Application Networking ManagerApplication · Cisco
CVE-2009-0617
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 Application Networking Manager (ANM) before 2.0 uses a default MySQL root password, which makes it easier for remote attackers to execute arbitrary operating-system commands or change system files.
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 Application Networking Manager (ANM) versions prior to 2.0 ship with a hardcoded default MySQL root password. Attackers who discover this password (widely known since this is a public disclosure) can authenticate to the MySQL database and leverage database features to execute operating-system commands or modify system files on the host.
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 Networking ManagerApplication
<= 1.2= 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
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check ANM versionLocate the Cisco ANM installation and retrieve its version number (check installation directory, version file, or application metadata)Affected if Version is 1.1, 1.2, or any version <= 1.2
-
Verify MySQL is runningIdentify and confirm the MySQL service associated with ANM is running on the systemAffected if MySQL service is active and accepting connections
-
Test default credential accessAttempt MySQL authentication using the publicly documented default root password for ANMAffected if Authentication succeeds with the default password, indicating the vulnerability is present
Environment is affected if ANM version is 1.1 or 1.2 (or <= 1.2) AND MySQL accepts the known default root password.
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.
dbcve · scopedUpgrade to ANM 2.0 or later, which eliminates the default password. For legacy systems, change the MySQL root password immediately to a strong, unique credential and audit for any unauthorized access.
Cisco ANM 2.0 or later
- 1. Identify current Cisco ANM version by accessing the ANM web interface or checking system information
- 2. If version is 1.1, 1.2, or any version before 2.0, plan for upgrade to version 2.0 or later
- 3. Backup current ANM configuration and database before upgrade
- 4. Obtain Cisco ANM version 2.0 or later from Cisco (requires valid support contract)
- 5. Perform upgrade following Cisco upgrade documentation
- 6. After upgrade, verify MySQL configuration no longer uses default credentials
- 7. As a security best practice, verify/change MySQL root password to a strong, unique value
- 8. Confirm ANM functionality is normal after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Application Networking Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0617 — 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-2009-0617 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