CVE-2020-15260 json
Existing TLS connections can be reused without checking remote hostname
published 2021-03-10 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-7269
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In version 2.10 and earlier, PJSIP transport can be reused if they have the same IP address + port + protocol. However, this is insufficient for secure transport since it lacks remote hostname authentication. Suppose we have created a TLS connection to `sip.foo.com`, which has an IP address `100.1.1.1`. If we want to create a TLS connection to another hostname, say `sip.bar.com`, which has the same IP address, then it will reuse that existing connection, even though `100.1.1.1` does not have certificate to authenticate as `sip.bar.com`. The vulnerability allows for an insecure interaction without user awareness. It affects users who need access to connections to different destinations that translate to the same address, and allows man-in-the-middle attack if attacker can route a connection to another destination such as in the case of DNS spoofing.
Patch / fix
- ring Debian 12 20210112.2.b757bac~ds1-1
debian advisories DEBIAN-CVE-2020-15260
- pjproject Ubuntu Pro 16.04 LTS 2.1.0.0.ast20130823-1+deb8u1ubuntu0.1~esm1
- pjproject Ubuntu Pro 18.04 LTS 2.7.2~dfsg-1ubuntu0.1~esm1
ubuntu advisories UBUNTU-CVE-2020-15260
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- pjproject Alpine 3.24, Alpine 3.23, Alpine 3.22 +8 more 2.11-r0
alpine advisories ALPINE-CVE-2020-15260
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-15260 updated cvss 6.8
pjproject: existing TLS connections can be reused without checking remote hostname
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N |
| NVD | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- pjsip pjproject
Classification
References
-
github.com
/pjsip/pjproject/commit/67e46c1ac45ad784db5b9080f5ed8b133c122872
patch, third-party-advisory
-
github.com
/pjsip/pjproject/pull/2663
patch, third-party-advisory
-
github.com
/pjsip/pjproject/security/advisories/GHSA-8hcp-hm38-mfph
patch, third-party-advisory
-
security.gentoo.org
/glsa/202107-42
vendor-advisory, third-party-advisory
Sources
- CVE List CVE-2020-15260
- NVD CVE-2020-15260
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.