# CVE-2017-16875: Integer overflow in n/a

> An attacker can trigger an integer overflow in PJSIP's ioqueue component via specific socket sequences, causing a denial of service by rejecting future key registrations.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qw72-xqg4-c435, UBUNTU-CVE-2017-16875

## What is CVE-2017-16875?

CVE-2017-16875 is a high-severity vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Teluu pjproject (pjlib and pjlib-util) in PJSIP before 2.7.1. The ioqueue component may issue a double key unregistration after an attacker initiates a socket connection with specific settings and sequences. Such double key unregistration will trigger an integer overflow, which may cause ioqueue backends to reject future key registrations.

## Which versions are affected by CVE-2017-16875?

It affects 1 product.


Products: Teluu Pjsip.

## How do I fix CVE-2017-16875?

Upgrade to a fixed version.

## Is CVE-2017-16875 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-38703](https://insights.sbomify.com/CVE-2023-38703/): PJSIP has use-after-free vulnerability in SRTP media transport (critical 9.8)
- [CVE-2022-39269](https://insights.sbomify.com/CVE-2022-39269/): Media transport downgrade from the secure version (SRTP) to non-secure (RTP) in pjsip (critical 9.1)
- [CVE-2026-57161](https://insights.sbomify.com/CVE-2026-57161/): PJSIP: Stack overflow handling Service-Route headers in a registration response (high 8.8)
- [CVE-2026-57162](https://insights.sbomify.com/CVE-2026-57162/): PJSIP: Stack overflow parsing SDP a=crypto attributes (high 8.8)
- [CVE-2026-57163](https://insights.sbomify.com/CVE-2026-57163/): PJSIP: Stack overflow parsing a TLS peer certificate's SubjectAltName in GnuTLS backend (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16875 and fix it if it is affected.

What it is: CVE-2017-16875 is a high-severity vulnerability in n/a, published on 17 Nov 2017. 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-2017-16875 in the wild and no public exploit code.

Affected product: n/a. 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-2017-16875/ (Markdown: https://insights.sbomify.com/CVE-2017-16875/index.md)
```

## Sources

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

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