Spa112 FirmwareOperating system · Cisco
CVE-2019-1683
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 certificate handling component of the Cisco SPA112, SPA525, and SPA5X5 Series IP Phones could allow an unauthenticated, remote attacker to listen to or control some aspects of a Transport Level Security (TLS)-encrypted Session Initiation Protocol (SIP) conversation. The vulnerability is due to the improper validation of server certificates. An attacker could exploit this vulnerability by crafting a malicious server certificate to present to the client. An exploit could allow an attacker to eavesdrop on TLS-encrypted traffic and potentially route or redirect calls initiated by an affected device. Affected software include version 7.6.2 of the Cisco Small Business SPA525 Series IP Phones and Cisco Small Business SPA5X5 Series IP Phones and version 1.4.2 of the Cisco Small Business SPA500 Series IP Phones and Cisco Small Business SPA112 Series IP Phones.
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 confidenceThe vulnerability exists in the certificate validation component of Cisco SPA112, SPA525, and SPA5X5 Series IP Phones. The phones fail to properly validate server certificates during TLS handshake for SIP connections, allowing a man-in-the-middle attacker to present a malicious certificate and intercept or redirect encrypted SIP traffic.
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.2
Spa525 FirmwareOperating system
= 7.6.2
Spa5x5 FirmwareOperating system
= 7.6.2
Spa500 FirmwareOperating system
= 1.4.2
Spa500s FirmwareOperating system
= 1.4.2
Spa500ds FirmwareOperating system
= 1.4.2
Spa501g FirmwareOperating system
= 1.4.2
Spa502g FirmwareOperating system
= 1.4.2CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 phone modelAccess the phone's web interface (http://<phone_ip>) and navigate to System > Product ID, or press the setup button on the phone and check System menu for model information. Alternatively, check the physical device label on the phone.Affected if model is one of SPA112, SPA525, SPA5X5, SPA500, SPA500s, SPA500ds, SPA501g, or SPA502g
-
Check the installed firmware versionIn the phone web interface, go to Info > Firmware Version (or Admin Login > System > Firmware Version). On the physical phone, press Setup button and navigate to Firmware Version in the Status menu. Record the exact version string shown.Affected if firmware version equals exactly 1.4.2 (for SPA112, SPA500, SPA500s, SPA500ds, SPA501g, SPA502g) or equals exactly 7.6.2 (for SPA525, SPA5X5)
-
Verify SIP over TLS is enabledIn the phone web interface, go to Ext(1) > SIP Settings > SIP Transport, or navigate to Phone > SIP Settings and check if Transport is set to TLS (or TLS/TCP). Confirm that the phone is configured to use encrypted SIP connections.Affected if SIP Transport is set to TLS or TLS/TCP (the vulnerability only applies when the phone uses TLS for SIP connections)
-
Confirm SIP server configurationIn the phone web interface, go to Ext(1) > Proxy and Registration, or Phone > SIP Server settings. Verify the SIP proxy/registrar hostname or IP address is configured. This confirms the phone is attempting to register with a SIP server over the network.Affected if a SIP proxy or registrar is configured (the phone must be registering to a SIP server for the TLS validation flaw to be exploitable)
You are affected if your phone model is SPA112, SPA525, SPA5X5, SPA500, SPA500s, SPA500ds, SPA501g, or SPA502g AND the firmware version is exactly 1.4.2 or 7.6.2 AND the phone has SIP over TLS enabled with a configured SIP server.
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 dataApply Cisco firmware updates for affected phone models (7.6.2 for SPA525/SPA5X5, 1.4.2 for SPA500/SPA112) to remediate the certificate validation flaw. Until patched, restrict phone network access to trusted VLANs and verify SIP server certificates are from trusted CAs.
Fix this in Spa112 Firmware
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1683 — 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-1683 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