CVE-2024-20489
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 · uneditedA vulnerability in the storage method of the PON Controller configuration file could allow an authenticated, local attacker with low privileges to obtain the MongoDB credentials. This vulnerability is due to improper storage of the unencrypted database credentials on the device that is running Cisco IOS XR Software. An attacker could exploit this vulnerability by accessing the configuration files on an affected system. A successful exploit could allow the attacker to view MongoDB credentials.
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 confidenceThe PON Controller in Cisco IOS XR Software stores MongoDB credentials in plaintext within configuration files. A local attacker with low-level authenticated access can read these unencrypted credentials directly from the configuration files on disk.
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= 24.1.1= 24.1.2= 24.2.1= 24.2.11= 24.3.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Identify PON Controller module presenceVerify if the PON Controller feature is enabled in your Cisco IOS XR configuration. This is typically checked via CLI commands that list enabled components or feature flags.Affected if PON Controller is enabled and the IOS XR version matches 24.1.1, 24.1.2, 24.2.1, 24.2.11, or 24.3.1
-
Confirm IOS XR versionRun the command to display the installed Cisco IOS XR version (for example, 'show version' or similar available command). Compare the output against the affected versions: 24.1.1, 24.1.2, 24.2.1, 24.2.11, 24.3.1Affected if The installed version exactly matches one of these version numbers
-
Locate configuration files containing MongoDB credentialsSearch configuration files on the system for plaintext MongoDB connection strings or credential fields. Examine files that store PON Controller or database configuration.Affected if Configuration files contain MongoDB credentials stored in plaintext (unencrypted) rather than being encrypted or masked
-
Verify file access controlsInspect file permissions on the configuration directories to determine which local users have read access to files that may contain MongoDB credentials.Affected if Low-privilege authenticated users have read access to configuration files containing plaintext MongoDB credentials
You are affected if PON Controller is enabled on Cisco IOS XR version 24.1.1, 24.1.2, 24.2.1, 24.2.11, or 24.3.1 and configuration files contain unencrypted MongoDB credentials accessible to local users.
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 · scopedApply the vendor patch when available and rotate all MongoDB credentials. Until patch deployment, restrict local access to configuration files and monitor for unauthorized access attempts.
Cisco IOS XR 24.3.1 or later (any 24.3.x maintenance release)
- Verify the current Cisco IOS XR version using 'show version' command
- Backup current configuration using 'admin export configuration' or 'copy running-config tftp://'
- Plan maintenance window for upgrade as this requires system reload
- Download the fixed IOS XR release (24.3.1 or later) from Cisco software downloads
- Upgrade the device using 'install add file' followed by 'install activate' and 'install commit' commands
- After reboot, verify the new version with 'show version' and confirm the vulnerability is resolved by checking for updated PON Controller configuration handling
- Validate that MongoDB credentials are now properly encrypted/hashed in configuration files
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-20489 — 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-2024-20489 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