Ata 191 FirmwareOperating system · Cisco
CVE-2024-20463
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 modify the configuration or reboot an affected device. This vulnerability is due to the HTTP server allowing state changes in GET requests. An attacker could exploit this vulnerability by sending a malicious request to the web-based management interface on an affected device. A successful exploit could allow the attacker to make limited modifications to the configuration or reboot the device, resulting in a denial of service (DoS) condition.
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 vulnerability exists in the web-based management interface of Cisco ATA 190 Series Analog Telephone Adapters. The HTTP server improperly allows state-changing operations (configuration modifications and device reboot) in GET requests, which violates HTTP specifications where GET should be idempotent and safe. An unauthenticated remote attacker can send malicious GET requests to trigger these state changes, causing denial of service.
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
Ata 191 FirmwareOperating system
< 12.0.2< 11.2.5
Ata 192 FirmwareOperating system
< 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
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 device modelAccess the device's web interface or check the physical device label to confirm whether it is a Cisco ATA 191 or ATA 192 Analog Telephone AdapterAffected if The device is not an ATA 191 or ATA 192 model (other models are not affected by this CVE)
-
Determine the installed firmware versionLog into the web-based management interface and navigate to the System Overview or Administration section to view the current firmware version; alternatively, use the device's CLI and run 'show version' or 'show firmware'Affected if The 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-based management interface is enabledCheck the device's web server configuration through the management interface under Administration > HTTP Server or similar, or via CLI with 'show http-server'Affected if The HTTP server for web management is enabled (the vulnerability only applies when the web interface is active)
-
Assess network exposure of the management interfaceReview firewall rules, ACLs, or network segmentation configurations to determine if the web management port (typically 80/443) is accessible from untrusted networks or the internetAffected if The web management interface is reachable from untrusted networks (an unauthenticated attacker must be able to send HTTP GET requests to exploit this vulnerability)
A user is affected if they have a Cisco ATA 191 or ATA 192 device running vulnerable firmware (below 12.0.2 for ATA 191, below 11.2.5 for ATA 192) with the web-based management interface enabled and exposed to untrusted networks where an unauthenticated attacker could send malicious GET requests.
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 firmware update when available; until then, restrict access to the web-based management interface using network segmentation, firewall rules, or ACLs to limit exposure to untrusted networks.
ATA 191: upgrade to firmware 12.0.2 or 11.2.5; ATA 192: upgrade to firmware 11.2.5
- 1. Identify the exact model (ATA 191 or ATA 192) and current firmware version of the affected device
- 2. Access the device's web-based management interface
- 3. Navigate to the firmware upgrade or administration section
- 4. Download the appropriate firmware from Cisco's official support site (sec.cloudapps.cisco.com)
- 5. Upload and apply the firmware upgrade
- 6. Verify the upgrade was successful by checking the firmware version in the web interface
- 7. Confirm the device is functioning normally after reboot
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ata 191 Firmware
Scoped from the published advisory
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20463 — 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-20463 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