# CVE-2019-1683: Cisco SPA112, SPA525, and SPA5x5 Series IP Phones Certificate Validation Vulnerability

> An attacker can bypass TLS certificate validation to eavesdrop on or redirect SIP calls on affected Cisco IP phones.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-jhfq-9hcr-5qqv

## What is CVE-2019-1683?

CVE-2019-1683 is a medium-severity vulnerability in Cisco Small Business SPA112 Series IP Phones, published on 25 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2019-1683?

It affects 14 products.


Products: Cisco Spa112 Firmware, Cisco Spa500 Firmware, Cisco Spa500ds Firmware, Cisco Spa500s Firmware, Cisco Spa501g Firmware, Cisco Spa502g Firmware, Cisco Spa504g Firmware, Cisco Spa508g Firmware, Cisco Spa509g Firmware, Cisco Spa512g Firmware, Cisco Spa514g Firmware, Cisco Spa525 Firmware, Cisco Spa525g Firmware, Cisco Spa5x5 Firmware.

## How do I fix CVE-2019-1683?

No fix has been published for CVE-2019-1683 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-1683 being exploited?

There is no known exploitation of CVE-2019-1683 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Small Business SPA112 Series IP Phones

- [CVE-2023-20126](https://insights.sbomify.com/CVE-2023-20126/): Cisco SPA112 2-Port Phone Adapters Remote Command Execution Vulnerability (critical 9.8)
- [CVE-2019-15240](https://insights.sbomify.com/CVE-2019-15240/): Cisco SPA100 Series Analog Telephone Adapters Remote Code Execution Vulnerabilities (high 8.0)
- [CVE-2019-15241](https://insights.sbomify.com/CVE-2019-15241/): Cisco SPA100 Series Analog Telephone Adapters Remote Code Execution Vulnerabilities (high 8.0)
- [CVE-2019-15242](https://insights.sbomify.com/CVE-2019-15242/): Cisco SPA100 Series Analog Telephone Adapters Remote Code Execution Vulnerabilities (high 8.0)
- [CVE-2019-15243](https://insights.sbomify.com/CVE-2019-15243/): Cisco SPA100 Series Analog Telephone Adapters Remote Code Execution Vulnerabilities (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1683 and fix it if it is affected.

What it is: CVE-2019-1683 is a medium-severity vulnerability in Cisco Small Business SPA112 Series IP Phones, published on 25 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1683 in the wild and no public exploit code.

Affected product: Cisco Small Business SPA112 Series IP Phones. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-1683/ (Markdown: https://insights.sbomify.com/CVE-2019-1683/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1683
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1683
- OSV: https://osv.dev/vulnerability/CVE-2019-1683

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1683/
Summaries are generated and may contain mistakes; the official description above is the record.