Ata 191 FirmwareOperating system · Cisco
CVE-2024-20420
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 authenticated, remote attacker with low privileges to run commands as an Admin user. This vulnerability is due to incorrect authorization verification by the HTTP server. An attacker could exploit this vulnerability by sending a malicious request to the web-based management interface. A successful exploit could allow the attacker to run commands as the Admin user.
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 confidenceThis is a privilege escalation vulnerability in the web-based management interface of Cisco ATA 190 Series Analog Telephone Adapters. The HTTP server performs incorrect authorization verification, allowing an authenticated attacker with low-privilege user credentials to execute arbitrary commands with Admin-level privileges by sending specially crafted HTTP requests.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 it is a Cisco ATA 191 or Cisco ATA 192 Analog Telephone AdapterAffected if The device is an ATA 191 or ATA 192 model
-
Check the installed firmware versionLog into the web-based management interface and navigate to the System Overview or Administration > Firmware Upgrade page to view the current firmware version. Alternatively, use the device's CLI and run 'show version' or check via the administration interface.Affected if The firmware version is below 12.0.2 or 11.2.5 for ATA 191, or below 11.2.5 for ATA 192
-
Confirm the web-based management interface is enabledAccess the device's web interface using its IP address. If the HTTP login page loads, the web management interface is enabled. Also check under Administration > Management Access > Web Server to verify the status.Affected if The web-based management interface is accessible and enabled on the device
-
Identify user accounts and their privilege levelsNavigate to Administration > User Management or similar section in the web interface to list configured users. Check for accounts with non-Admin (such as User or Viewer) privilege levels.Affected if There are low-privilege user accounts configured on the device in addition to Admin accounts
The device is affected if it is an ATA 191 or ATA 192 running firmware versions below 12.0.2 (or 11.2.5 for ATA 191) or below 11.2.5 (for ATA 192), and the web-based management interface is enabled with at least one low-privilege user account present.
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 from Cisco. If no patch is immediately available, restrict access to the web-based management interface to trusted networks or disable it entirely until the update can be deployed.
Cisco ATA 191: upgrade to firmware 12.0.2 or 11.2.5; Cisco ATA 192: upgrade to firmware 11.2.5
- Download the fixed firmware version (12.0.2 for ATA 191 or 11.2.5 for ATA 191/192) from Cisco's official download page at sec.cloudapps.cisco.com
- Log in to the web-based management interface of the affected Cisco ATA device
- Navigate to the Administration > Firmware Upgrade (or similar) section
- Upload the downloaded firmware file
- Apply the firmware upgrade and wait for the device to reboot
- Verify the firmware version has been updated to the fixed release
- Confirm the web-based management interface is accessible and functioning correctly
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
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20420 — 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-20420 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