Existing TLS connections can be reused without checking remote hostname
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
2Patches
Vulnerability mechanics
References
4- security.gentoo.org/glsa/202107-42mitrevendor-advisoryx_refsource_GENTOO
- github.com/pjsip/pjproject/commit/67e46c1ac45ad784db5b9080f5ed8b133c122872mitrex_refsource_MISC
- github.com/pjsip/pjproject/pull/2663mitrex_refsource_MISC
- github.com/pjsip/pjproject/security/advisories/GHSA-8hcp-hm38-mfphmitrex_refsource_CONFIRM
News mentions
0No linked articles in our index yet.