Spa112 FirmwareOperating system · Cisco
CVE-2019-15257
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 · uneditedA vulnerability in the web-based management interface of Cisco SPA100 Series Analog Telephone Adapters (ATAs) could allow an authenticated, remote attacker to access sensitive information on an affected device. The vulnerability is due to improper restrictions on configuration information. An attacker could exploit this vulnerability by sending a request to an affected device through the web-based management interface. A successful exploit could allow the attacker to return running configuration information that could also include 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 · moderate confidenceThe vulnerability exists in the web-based management interface of Cisco SPA100 Series ATAs. An authenticated attacker can send specific requests to the web interface to retrieve running configuration data, which may contain sensitive information such as credentials or system details. This is due to insufficient access controls on configuration export or viewing functionality.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the device admin interface or check the physical device label to confirm whether it is a Cisco SPA112 or SPA122 ATAAffected if The device is a Cisco SPA112 or SPA122 model
-
Check firmware versionLog into the web-based management interface and navigate to the Administration or Status section to view the firmware version. Compare this against the affected versions: any version < 1.4.1 or exactly version 1.4.1Affected if The firmware version is 1.4.1 or any version lower than 1.4.1
-
Verify web management interface is enabledAttempt to access the device web interface via its IP address (typically http://[device IP]) or check the device configuration for HTTP/HTTPS management access settingsAffected if The web-based management interface is accessible and enabled
-
Confirm configuration export feature existsWithin the web management interface, look for any configuration backup, export, or save configuration functionality (often under Administration, System, or Backup/Restore sections)Affected if The configuration export or viewing functionality is present and accessible to authenticated users
The environment is affected if the device is a Cisco SPA112 or SPA122 running firmware version 1.4.1 or lower, with the web management interface enabled and accessible to users.
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
Apply the latest Cisco firmware update for SPA100 Series devices when available. Until then, restrict web management interface access to trusted networks or IP addresses, and use strong authentication credentials.
Fix this in Spa112 Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15257 — 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-15257 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