Spa112 FirmwareOperating system · Cisco
CVE-2019-15250
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 · uneditedMultiple 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 confidenceMultiple input validation flaws in the web-based management interface of Cisco SPA100 Series ATAs allow authenticated attackers to inject malicious commands. An adjacent attacker with valid credentials can send specially crafted HTTP requests to execute arbitrary code with elevated (root) privileges on the affected device.
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
< 1.4.1= 1.4.1
Spa122 FirmwareOperating system
< 1.4.1= 1.4.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the label on the physical device or access the web interface login page for the model number. The vulnerability affects only Cisco SPA112 and SPA122 ATAs.Affected if The device is not a Cisco SPA112 or SPA122 ATA
-
Check the firmware versionLog into the web-based management interface and navigate to the Administration or System Information page to view the firmware version. Alternatively, check the device label or documentation.Affected if Firmware version is 1.4.1 or lower (less than 1.4.1 or exactly 1.4.1)
-
Verify web-based management interface is enabledCheck the device configuration for HTTP/HTTPS management access settings. This is typically found under Administration > Web Access or similar menu path.Affected if Web-based management interface is enabled and accessible over HTTP or HTTPS
-
Confirm credential statusDetermine if default administrator credentials are still in use, or if valid credentials exist for any user with management access. Check if the default user/admin account remains unchanged.Affected if Valid credentials exist for the web management interface (default credentials or otherwise)
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 using valid credentials.
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.
From vendor data1.4.1
Disable the web-based management interface if not required, or restrict access to trusted networks only. Apply Cisco firmware updates when available. If the web interface must remain enabled, monitor for anomalous requests and change default credentials immediately.
Fix this in Spa112 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15250 — 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-2019-15250 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