Spa112 FirmwareOperating system · Cisco

CVE-2019-15248

HIGH · 8.0 CVSS v3.1 Published 2019-10-16
Fix available
A fix is available. Upgrade to 1.4.1 or later.
See remediation →
82/100
Remediation priority · High
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 Cisco SPA100 Series Analog Telephone Adapters (ATAs) could allow an authenticated, adjacent attacker to execute arbitrary code with elevated privileges. The vulnerabilities are due to improper validation of user-supplied input to the web-based management interface. An attacker could exploit these vulnerabilities by authenticating to the web-based management interface and sending crafted requests to an affected device. A successful exploit could allow the attacker to execute arbitrary code with elevated privileges. Note: The web-based management interface is enabled by default.

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 input validation vulnerabilities in the web-based management interface of Cisco SPA100 Series Analog Telephone Adapters allow an authenticated, adjacent attacker to execute arbitrary code with elevated privileges. The vulnerabilities stem from improper validation of user-supplied input in HTTP requests to the web interface, which is enabled by default. An attacker with valid credentials and network adjacency to the device can inject malicious input to achieve code execution with elevated (root) privileges.

MitigationDisable the web-based management interface if not required, restrict access to trusted IP addresses via ACLs, enforce strong authentication credentials, and apply Cisco-provided firmware patches when available. Network segmentation can limit the adjacent attack surface.

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

CVSS:3.1/AV:A/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. Confirm device model
    Check the physical device label or access the web interface to identify if the device is a Cisco SPA112 or SPA122 Analog Telephone Adapter.
    Affected if Device is a Cisco SPA112 or SPA122 model
  2. Check installed firmware version
    Access the device web interface and navigate to the Administration or Status page to view the firmware version. Compare against affected versions 1.4.1 and below.
    Affected if Firmware version is 1.4.1 or lower (< 1.4.1 or = 1.4.1)
  3. Verify web management interface is enabled
    Attempt to access the device IP address via HTTP (port 80) or HTTPS (port 443) from a connected system. If a login page loads or the interface responds, web management is enabled.
    Affected if Web-based management interface is accessible and responding

Device is affected if it is a Cisco SPA112 or SPA122 running firmware version 1.4.1 or lower and the web management interface is enabled (which is the default state).

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

Disable the web-based management interface if not required, restrict access to trusted IP addresses via ACLs, enforce strong authentication credentials, and apply Cisco-provided firmware patches when available. Network segmentation can limit the adjacent attack surface.

Fix this in Spa112 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15248 — 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-15248 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