CVE-2017-16875

CVE-2017-16875 is a high-severity vulnerability in Teluu Pjsip with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

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.

Frequently asked questions

What is CVE-2017-16875?
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.
How severe is CVE-2017-16875?
CVE-2017-16875 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2017-16875 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-16875?
CVE-2017-16875 affects Teluu Pjsip. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-16875?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-16875 published?
CVE-2017-16875 was published on 2017-11-17 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Teluu Pjsip

All CVEs affecting Teluu Pjsip →