Ata 190 FirmwareOperating system · Cisco

CVE-2021-34710

HIGH · 8.8 CVSS v3.1 Published 2021-10-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Multiple vulnerabilities in the Cisco ATA 190 Series Analog Telephone Adapter Software could allow an attacker to perform a command injection attack resulting in remote code execution or cause a denial of service (DoS) condition on an affected device. For more information about these vulnerabilities, see the Details section of this advisory.

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 · moderate confidence

Multiple vulnerabilities in Cisco ATA 190 Series Analog Telephone Adapter software allow command injection attacks, potentially enabling remote code execution (RCE) or denial of service (DoS) conditions on affected devices. The vulnerabilities stem from insufficient input validation in the device firmware, allowing attackers to inject arbitrary commands through the web interface or other attack vectors.

MitigationApply the vendor-supplied firmware update from Cisco for the ATA 190 Series devices. If patches are unavailable, restrict network access to management interfaces and monitor for indicators of compromise.

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 190 FirmwareOperating system
Affected:all versions
Ata 191 FirmwareOperating system
Affected:all versions
Ata 192 FirmwareOperating system
Affected:all versions

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
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 checks

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

  1. Identify Cisco ATA 190 Series device model
    Access the device web interface or check physical device label for model number (ATA 190, ATA 191, or ATA 192)
    Affected if Device model is ATA 190, ATA 191, or ATA 192 Series Analog Telephone Adapter
  2. Determine firmware version
    Log into the device web interface and navigate to System > Software or check the firmware version displayed on the main status page
    Affected if Any firmware version is installed on an affected ATA 190/191/192 device (all versions are vulnerable)
  3. Verify web management interface accessibility
    Check if the device HTTP/HTTPS management interface is exposed to untrusted networks by reviewing firewall rules or network configuration
    Affected if Web interface is accessible from untrusted networks (internet-facing or unsecured internal segments)
  4. Review device for signs of compromise
    Check device configuration for unexpected changes, new user accounts, or suspicious processes; review system logs for unfamiliar commands or authentication attempts from unknown sources
    Affected if Unexpected configuration changes, unknown administrative accounts, or suspicious activity logs are present

Users are affected if they have any Cisco ATA 190, ATA 191, or ATA 192 device running any firmware version with an accessible management interface.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware update from Cisco for the ATA 190 Series devices. If patches are unavailable, restrict network access to management interfaces and monitor for indicators of compromise.

Fix this in Ata 190 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34710 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-34710 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