Ata 191 FirmwareOperating system · Cisco
CVE-2024-20459
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 Multiplatform Series Analog Telephone Adapter firmware could allow an authenticated, remote attacker with high privileges to execute arbitrary commands as the root user on the underlying operating system. This vulnerability is due to a lack of input sanitization in the web-based management interface. 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 execute arbitrary commands on the underlying operating system as the root 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 confidenceCommand injection vulnerability in Cisco ATA 190 web-based management interface allows authenticated attackers with high privileges to execute arbitrary commands as root due to insufficient input sanitization in the web interface.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 Cisco ATA device web interface or use the device's administration page to confirm the model number is ATA 191 or ATA 192Affected if The device is a Cisco ATA 191 or ATA 192 model
-
Check the installed firmware versionNavigate to the device web interface (typically https://<device-ip>/) and look for the firmware version in the status or administration section, or use the CLI command 'show version' via telnet/SSH if availableAffected if The firmware version is below 12.0.2 (for ATA 191) or below 11.2.5 (for ATA 191 or ATA 192)
-
Confirm web-based management interface is accessibleVerify that the web management interface (HTTP/HTTPS on port 443 or 80) is enabled and reachable on the device. Check under Administration > Network Setup or similar management settingsAffected if The web-based management interface is enabled and exposed on the network
-
Verify presence of high-privilege accountsCheck the device user accounts through the web interface under Administration > User Management or similar, noting accounts with administrative or root-level privilegesAffected if There are accounts with high privileges (administrator/root) configured on the device
The environment is affected if the device is a Cisco ATA 191 or ATA 192 running firmware below 12.0.2 (ATA 191) or below 11.2.5 (both models), with the web management interface enabled and accessible to an authenticated attacker with high privileges.
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
Restrict web management interface access to trusted networks/IPs; apply Cisco firmware patches when available; audit accounts with high privileges.
Cisco ATA 191: firmware 12.0.2 or later (or 11.2.5 or later); Cisco ATA 192: firmware 11.2.5 or later
- 1. Identify the exact model (ATA 191 or ATA 192) of the Cisco Analog Telephone Adapter in your environment
- 2. Access the web-based management interface of the affected device
- 3. Navigate to the firmware upgrade section (typically under Administration > System Software > Upgrade)
- 4. Download the appropriate fixed firmware version from Cisco's official support site (sec.cloudapps.cisco.com)
- 5. Upload and apply the firmware upgrade: For ATA 191, upgrade to version 12.0.2 or later (or 11.2.5 or later); For ATA 192, upgrade to version 11.2.5 or later
- 6. Verify the upgrade was successful by confirming the new firmware version in the web interface
- 7. Reboot the device if prompted to ensure all changes take effect
- 8. Validate that the web-based management interface is functioning correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ata 191 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20459 — 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-20459 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