Existing TLS connections can be reused without checking remote hostname
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-295.
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Advisory ·
pjsip pjproject — GLSA-202107-42
2 records Highest priority Priority LOW 2 LOW
Other records, highest priority first
- TI-2021-04474 Crash in receiving updated SDP answer after initial SDP negotiation failedPriority LOW 33
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2020-15260
References
More pjsip vulnerabilities
- TI-2022-13076 Potential stack buffer overflow when parsing message as a STUN client CVSS 3.1CRITICAL 9.8
- TI-2022-08599 Potential out-of-bound read/write in PJSIP CVSS 3.1CRITICAL 9.8
- TI-2023-20051 PJSIP has use-after-free vulnerability in SRTP media transport CVSS 3.1CRITICAL 9.8
- TI-2022-06096 Out-of-bounds read in multipart parsing in PJSIP CVSS 3.1CRITICAL 9.1
- TI-2022-07661 Use after free in PJSIP CVSS 3.1CRITICAL 9.8
- TI-2022-06095 Potential out-of-bound read during RTP/RTCP parsing in PJSIP CVSS 3.1CRITICAL 9.1
Sources
- CVE-2020-15260 · CVE Program
- CVE-2020-15260 · NVD
- FIRST EPSS
- CVE-2020-15260 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences