Skip to content

Existing TLS connections can be reused without checking remote hostname

Moderate
sauwming published GHSA-8hcp-hm38-mfph Mar 8, 2021

Package

No package listed

Affected versions

2.10 or lower

Patched versions

2.11

Description

Currently, 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.

Impact

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.

Patches

The fix is available in commit 67e46c1 and #2663.

Workarounds

Guard against DNS spoofing.

References

For more information

If you have any questions or comments about this advisory:

CVE ID

CVE-2020-15260

Credits