dbcve.org
Ata 191 FirmwareOperating system · Cisco

CVE-2024-20461

MEDIUM · 6.0 CVSS v3.1 Published 2024-10-16
Fix available
A fix is available. Upgrade to 11.2.5 / 12.0.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Zero-click

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 · unedited
A vulnerability in the CLI of Cisco ATA 190 Series Analog Telephone Adapter firmware could allow an authenticated, local attacker with high privileges to execute arbitrary commands as the root user. This vulnerability exists because CLI input is not properly sanitized. An attacker could exploit this vulnerability by sending malicious characters to the CLI. A successful exploit could allow the attacker to read and write to 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 confidence

This is a command injection vulnerability in the CLI of Cisco ATA 190 Series Analog Telephone Adapters. The CLI fails to properly sanitize user input, allowing an authenticated attacker with high privileges to inject and execute arbitrary operating system commands with root-level privileges.

MitigationApply the vendor patch when available; otherwise, restrict CLI access to trusted, minimum-privilege users and monitor for suspicious command activity.

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
Affected:< 12.0.2< 11.2.5
Ata 192 FirmwareOperating system
Affected:< 11.2.5

CVSS 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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Cisco ATA device model
    Access the device web interface or CLI and check the hardware model identifier (ATA 191 or ATA 192)
    Affected if The device is a Cisco ATA 191 or ATA 192 series adapter
  2. Check the installed firmware version
    In the web interface, navigate to System Settings > Software Version, or via CLI run 'show version'
    Affected if The firmware version is below 12.0.2 or 11.2.5 for the respective model
  3. Verify CLI access is enabled
    Check the device configuration for enablement of the CLI interface (typically via HTTP/HTTPS web interface under Administration > Management Access)
    Affected if The CLI management interface is accessible and authentication is possible
  4. Confirm privilege level of accessible accounts
    Review configured user accounts and their privilege levels in the device configuration
    Affected if There are accounts with high/Administrator privileges that can access the CLI

You are affected if you have a Cisco ATA 191 running firmware below 12.0.2 or below 11.2.5, or an ATA 192 running firmware below 11.2.5, and the CLI interface is accessible with high-privilege authenticated accounts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.2.5 / 12.0.2 or later
Fixed in 11.2.512.0.2
Interim mitigation

Apply the vendor patch when available; otherwise, restrict CLI access to trusted, minimum-privilege users and monitor for suspicious command activity.

Recommended fix High confidence

ATA 191: upgrade to 12.0.2 or later (or 11.2.5 or later); ATA 192: upgrade to 11.2.5 or later

  1. 1. Identify the exact model (ATA 191 or ATA 192) and current firmware version of your device
  2. 2. Access the device console or web interface with administrative credentials
  3. 3. Navigate to the firmware upgrade section in the device management interface
  4. 4. Download the appropriate firmware version from Cisco's official support site (sec.cloudapps.cisco.com)
  5. 5. Upload the firmware file and initiate the upgrade process
  6. 6. Wait for the device to reboot and verify the new firmware version is installed
  7. 7. Confirm the CLI now properly sanitizes input and the vulnerability is remediated
Caveat Standard firmware upgrade - review Cisco release notes for any configuration or feature changes before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ata 191 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20461 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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