Ata 191 FirmwareOperating system · Cisco
CVE-2024-20460
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 conduct a reflected cross-site scripting (XSS) attack against a user. This vulnerability is due to insufficient validation of user input. An attacker could exploit this vulnerability by persuading a user to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information on an affected device.
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 confidenceReflected XSS vulnerability in Cisco ATA 190 Series Analog Telephone Adapter web-based management interface due to insufficient user input validation. Unauthenticated remote attacker can inject malicious scripts via crafted URLs, executing in user browser context.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 device modelAccess the device web interface or check physical label. Look for 'Cisco ATA 191' or 'Cisco ATA 192' model designation.Affected if Device is NOT a Cisco ATA 191 or ATA 192 model (other models not listed as affected)
-
Determine firmware version via web interfaceLogin to the device web-based management interface. Navigate to Administration > Firmware or System Information page to view the installed firmware version.Affected if Firmware version cannot be determined or device web interface is inaccessible
-
Compare ATA 191 version against affected rangesIf device is Cisco ATA 191, compare installed firmware version to affected versions: any version below 12.0.2 or any version below 11.2.5 (both ranges affected). Note that 12.0.2 and 11.2.5 are the fixed releases.Affected if ATA 191 firmware version is below 12.0.2 OR below 11.2.5
-
Compare ATA 192 version against affected rangesIf device is Cisco ATA 192, compare installed firmware version to affected versions: any version below 11.2.5 is affected. Note that 11.2.5 is the fixed release.Affected if ATA 192 firmware version is below 11.2.5
-
Assess web interface exposureVerify whether the device web-based management interface is accessible from network locations where untrusted users could potentially submit crafted URLs.Affected if Web management interface is exposed to untrusted network segments or the internet
User is affected if they have a Cisco ATA 191 with firmware below 12.0.2 or below 11.2.5, or an ATA 192 with firmware below 11.2.5, AND the web interface is accessible to potential attackers.
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 Cisco-provided firmware patch when available; until then, users should avoid clicking untrusted links to the device management interface.
Cisco ATA 191: upgrade to firmware 12.0.2 or 11.2.5; Cisco ATA 192: upgrade to firmware 11.2.5
- 1. Identify the specific ATA model (191 or 192) from the device label or web interface
- 2. Determine the current firmware version by logging into the web-based management interface and checking the status or administration page
- 3. Download the appropriate fixed firmware version from the official Cisco software download center (requires valid Cisco service contract)
- 4. Navigate to the Administration > Firmware Upgrade or System Upgrade section in the web-based management interface
- 5. Upload the firmware file and initiate the upgrade process
- 6. Wait for the device to reboot and verify the new firmware version matches the fixed release (12.0.2 or 11.2.5)
- 7. Clear browser cache and cookies to remove any potentially malicious stored XSS data
- 8. Verify the device is functioning normally by testing basic call functionality
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
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20460 — 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-20460 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