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.
The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.
The product does not validate, or incorrectly validates, a certificate.
| Link | Tags |
|---|---|
| https://github.com/pjsip/pjproject/security/advisories/GHSA-8hcp-hm38-mfph | third party advisory patch |
| https://github.com/pjsip/pjproject/commit/67e46c1ac45ad784db5b9080f5ed8b133c122872 | third party advisory patch |
| https://github.com/pjsip/pjproject/pull/2663 | third party advisory patch |
| https://security.gentoo.org/glsa/202107-42 | third party advisory vendor advisory |