CVE-2020-15260: Existing TLS connections can be reused without checking remote hostname

Published Mar 10, 2021
·
Updated

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.

Affected Software

1 affected component
Teluu PJSIP<=2.10

Event History

Mar 10, 2021
CVE Published
via MITRE·10:30 PM
Data Sourced
via MITRE·10:30 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2020-15260?

CVE-2020-15260 is a vulnerability in PJSIP, a multimedia communication library, that allows reuse of transport with the same IP address, port, and protocol.

2

What is the severity of CVE-2020-15260?

CVE-2020-15260 has a severity rating of 6.8 (medium).

3

How does CVE-2020-15260 affect PJSIP?

CVE-2020-15260 affects PJSIP versions up to and including 2.10.

4

How can I fix CVE-2020-15260?

To fix CVE-2020-15260, it is recommended to update to a version of PJSIP that is not affected by the vulnerability.

5

Does CVE-2020-15260 require authentication?

CVE-2020-15260 does not require authentication, making it a potential security risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203