CVE-2024-20458
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 web-based management interface of Cisco ATA 190 Series Analog Telephone Adapter firmware could allow an unauthenticated, remote attacker to view or delete the configuration or change the firmware on an affected device. This vulnerability is due to a lack of authentication on specific HTTP endpoints. An attacker could exploit this vulnerability by browsing to a specific URL. A successful exploit could allow the attacker to view or delete the configuration or change the firmware.
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 confidenceThis is an authentication bypass vulnerability in the web-based management interface of Cisco ATA 190 Series Analog Telephone Adapters. The flaw stems from missing authentication checks on specific HTTP endpoints, allowing unauthenticated remote attackers to access these URLs to view or delete device configuration or upload arbitrary firmware images.
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< 12.0.2< 11.2.5< 11.2.5CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
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 the ATA device modelLocate the hardware model number on the device label or access the device CLI and run 'show version' to confirm the model is Cisco ATA 191 or ATA 192Affected if Device model is ATA 191 or ATA 192
-
Check the installed firmware versionAccess the web-based management interface and navigate to the System Information page, or use the CLI command 'show version' to retrieve the firmware version numberAffected if Firmware version is below 12.0.2 for ATA 191, or below 11.2.5 for either ATA 191 or ATA 192
-
Verify if the web management interface is enabledLog into the device CLI or web interface and check the HTTP/HTTPS service status under the management settingsAffected if The web-based management interface (HTTP or HTTPS) is enabled on the device
-
Assess network exposure of the web interfaceCheck the device network configuration to determine which IP addresses or networks can reach the web management interface. Review firewall rules or ACLs if the device is deployed behind a network perimeterAffected if The web management interface is accessible from untrusted networks or directly from the internet
Your environment is affected if you are running an ATA 191 or ATA 192 device with firmware below the fixed versions AND the web management interface is enabled, regardless of network exposure.
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 · scoped11.2.512.0.2
Apply the vendor-supplied firmware patch when available; until then, restrict network access to the device management interface using firewall rules or ACLs to prevent unauthorized access from untrusted networks.
Cisco ATA 191: upgrade to firmware 12.0.2 (or 11.2.5); Cisco ATA 192: upgrade to firmware 11.2.5
- Identify the exact model (ATA 191 or ATA 192) of the affected Cisco Analog Telephone Adapter
- Determine the current firmware version by accessing the web-based management interface or checking the device status
- For ATA 191 devices: Upgrade firmware to version 12.0.2 or later (or 11.2.5 or later if staying on 11.x branch)
- For ATA 192 devices: Upgrade firmware to version 11.2.5 or later
- Download firmware only from the official Cisco software download center (software.cisco.com)
- Access the web-based management interface and navigate to the Firmware Upgrade or Administration section
- Upload the downloaded firmware file and initiate the upgrade process
- Wait for the upgrade to complete and verify the device reboots successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20458 — 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-20458 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