{"id":"CVE-2020-15260","aliases":["ALPINE-CVE-2020-15260","DEBIAN-CVE-2020-15260","EUVD-2020-7269","GHSA-8hcp-hm38-mfph","MGASA-2021-0337","UBUNTU-CVE-2020-15260"],"status":"published","title":"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.","severity":{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00987,"percentile":0.62671,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-295","CWE-297"],"published":"2021-03-10T22:30:16Z","modified":"2026-10-26T12:00:23Z","fixes":[{"ecosystem":"Alpine:v3.14","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.15","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.16","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.17","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"pjproject","fixed_in":["2.11-r0"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"ring","fixed_in":["20210112.2.b757bac~ds1-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"pjproject","fixed_in":["2.1.0.0.ast20130823-1+deb8u1ubuntu0.1~esm1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"pjproject","fixed_in":["2.7.2~dfsg-1ubuntu0.1~esm1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.14","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.15","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.16","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11-r0"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"ring","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20210112.2.b757bac~ds1-1"}]}]},{"source":"osv","ecosystem":"Mageia:8","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.10-5.2.mga8"}]}],"bundled":2},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0.0.ast20130823-1+deb8u1ubuntu0.1~esm1"}]}],"versions":["2.1.0.0.ast20130823-1","2.1.0.0.ast20130823-1+deb8u1build0.16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"pjproject","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.2~dfsg-1ubuntu0.1~esm1"}]}],"versions":["2.6~dfsg-2","2.7~dfsg-1","2.7.1~dfsg-1","2.7.1~dfsg-1build1","2.7.2~dfsg-1"]}],"products":[{"vendor":"pjsip","product":"pjproject"},{"vendor":"teluu","product":"pjsip"}],"references":[{"url":"https://github.com/pjsip/pjproject/security/advisories/GHSA-8hcp-hm38-mfph","tags":["x_refsource_CONFIRM","x_transferred","Patch","Third Party Advisory","fix","advisory","report"]},{"url":"https://github.com/pjsip/pjproject/commit/67e46c1ac45ad784db5b9080f5ed8b133c122872","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix","report"]},{"url":"https://github.com/pjsip/pjproject/pull/2663","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix","report"]},{"url":"https://security.gentoo.org/glsa/202107-42","tags":["vendor-advisory","x_refsource_GENTOO","x_transferred","Third Party Advisory","advisory"]},{"url":"https://security.alpinelinux.org/vuln/CVE-2020-15260","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2020-15260","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2021-0337.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=28998","tags":["report"]},{"url":"https://github.com/pjsip/pjproject/security/advisories/GHSA-hvq6-f89p-frvp","tags":["advisory"]},{"url":"https://www.debian.org/lts/security/2021/dla-2636","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2020-15260","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2020-15260","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8122-1","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2020-15260","title":"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.","status":"published","published":"2021-03-10T22:30:16Z","modified":"2024-08-04T13:15:19.022Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-297"],"updated_at":"2026-11-02T14:35:50.228781Z"}],"euvd":[{"id":"EUVD-2020-7269","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.","status":"published","published":"2021-03-10T22:30:16Z","modified":"2024-08-04T13:15:19Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-03T03:07:31.955969Z"}],"nvd":[{"id":"CVE-2020-15260","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.","status":"published","published":"2021-03-10T23:15:12.3Z","modified":"2026-06-17T02:56:22.867Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium","assessor":"secondary"},{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium","assessor":"primary"},{"version":"2.0","score":4.3,"vector":"AV:N/AC:M/Au:N/C:N/I:P/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-297","CWE-295"],"updated_at":"2026-11-02T14:06:37.687844Z"}],"osv":[{"id":"ALPINE-CVE-2020-15260","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.","status":"published","published":"2021-03-10T23:15:12.3Z","modified":"2026-10-26T11:17:55.129820899Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:27:48.11886Z"},{"id":"CVE-2020-15260","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.","status":"published","published":"2021-03-10T23:15:12.3Z","modified":"2026-10-20T13:52:27.949499319Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:44:14.828228Z"},{"id":"DEBIAN-CVE-2020-15260","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.","status":"published","published":"2021-03-10T23:15:12.3Z","modified":"2026-10-26T12:00:23.460600665Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:45:33.384087Z"},{"id":"UBUNTU-CVE-2020-15260","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.","status":"published","published":"2021-03-10T23:15:00Z","modified":"2026-04-22T12:19:10.466443Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium"},{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:54:23.344108Z"},{"id":"MGASA-2021-0337","title":"Updated pjproject packages fix security vulnerabilities","description":"Currently, PJSIP transport can be reused if they have the same IP address\n+ port + protocol. However, this is insufficient for secure transport since\nit lacks remote hostname authentication. The vulnerability allows for an\ninsecure interaction without user awareness. It affects users who need access\nto connections to different destinations that translate to the same address,\nand allows man-in-the-middle attack if attacker can route a connection to\nanother destination such as in the case of DNS spoofing (CVE-2020-15260).\n\nAn issue has been found in pjproject. Due to bad handling of two consecutive\ncrafted answers to an INVITE, the attacker is able to crash the server\nresulting in a denial of service (CVE-2021-21375).\n","status":"published","published":"2021-07-10T20:00:34Z","modified":"2026-04-16T04:44:14.20493981Z","updated_at":"2026-11-02T15:49:41.509337Z"}]}}