Spa112 FirmwareOperating system · Cisco

CVE-2019-12704

MEDIUM · 6.5 CVSS v3.1 Published 2019-10-16
Fix available
A fix is available. Upgrade to 1.4.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A vulnerability in the web-based management interface of Cisco SPA100 Series Analog Telephone Adapters (ATAs) could allow an authenticated, remote attacker to view the contents of arbitrary files on an affected device. The vulnerability is due to improper input validation in the web-based management interface. An attacker could exploit this vulnerability by sending a crafted request to the web-based management interface of an affected device. A successful exploit could allow the attacker to retrieve the contents of arbitrary files on the device, possibly resulting in the disclosure of sensitive information.

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

Improper input validation in the web-based management interface of Cisco SPA100 Series ATAs allows an authenticated attacker to send crafted requests that bypass path restrictions, enabling arbitrary file read on the device filesystem. This is a local file inclusion/path traversal vulnerability requiring authentication.

MitigationApply the Cisco firmware patch when available; until then, restrict web management interface access to trusted networks only and use strong authentication credentials.

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
Spa112 FirmwareOperating system
Affected:< 1.4.1= 1.4.1
Spa122 FirmwareOperating system
Affected:< 1.4.1= 1.4.1

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 device model
    Check the product label or access the web management interface to confirm the device is a Cisco SPA112 or SPA122 ATA.
    Affected if Device is not a SPA112 or SPA122 model.
  2. Check the firmware version
    Access the web-based management interface and navigate to the Administration or System Information page to view the firmware version, or use the device's administrative CLI if available.
    Affected if Firmware version is 1.4.1 or earlier (including any version below 1.4.1).
  3. Verify web management interface is enabled
    Access the device configuration and check if the web-based management interface is enabled (typically under Administration > Web Management or similar settings).
    Affected if The web-based management interface is enabled and accessible.
  4. Confirm authentication is in use
    Verify that authentication is required to access the web management interface by attempting to access it without credentials.
    Affected if The web interface is accessible without authentication (though this would actually represent an additional vulnerability).

The environment is affected if the device is a Cisco SPA112 or SPA122 running firmware version 1.4.1 or earlier with the web-based management interface enabled and accessible, since an authenticated attacker could exploit the path traversal to read arbitrary files.

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
Upgrade available Upgrade to 1.4.1 or later
Fixed in 1.4.1
Interim mitigation

Apply the Cisco firmware patch when available; until then, restrict web management interface access to trusted networks only and use strong authentication credentials.

Fix this in Spa112 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 the upgrade done

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-2019-12704 — 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-2019-12704 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