Spa122 FirmwareOperating system · Cisco
CVE-2019-12703
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 SPA122 ATA with Router Devices could allow an unauthenticated, adjacent attacker to conduct cross-site scripting attacks. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of the affected software. An attacker could exploit this vulnerability by sending malicious input to the affected software through crafted DHCP requests, and then persuading a user to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based 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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in the web-based management interface of Cisco SPA122 ATA with Router Devices. An unauthenticated, adjacent attacker can inject malicious script through crafted DHCP requests. When a user clicks a crafted link, the malicious code executes in the context of the web interface, potentially allowing arbitrary script execution or access to sensitive browser-based information.
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
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 the device modelLocate the physical device or access the administrative interface and confirm the model number is Cisco SPA122 ATA with RouterAffected if The device is not a Cisco SPA122 ATA with Router - this CVE only applies to that specific model
-
Determine the firmware versionAccess the web-based management interface, navigate to the Admin or Status section, and locate the firmware version information. Alternatively, check the device label or documentationAffected if The installed firmware version is 1.4.1 or earlier (versions < 1.4.1 or = 1.4.1)
-
Confirm the web-based management interface is enabledAccess the device configuration and verify if the web-based management interface (HTTP/HTTPS) is currently enabled and accessibleAffected if The web interface is enabled and accessible - the XSS vulnerability exploits this interface to execute malicious scripts
-
Verify DHCP service is activeCheck the device network settings to confirm the DHCP server or DHCP client functionality is configured and activeAffected if DHCP is enabled - the vulnerability is injected through crafted DHCP requests that get stored and later executed when a user interacts with the web interface
You are affected if you have a Cisco SPA122 device running firmware version 1.4.1 or earlier with the web-based management interface enabled and DHCP functionality in use.
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 available Cisco firmware updates for SPA122 devices. If no update is available, disable the web-based management interface or restrict network access to trusted users to reduce the attack surface.
Fix this in Spa122 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-12703 — 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-12703 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