CVE-2020-26262: Loopback bypass in Coturn
Coturn is free open source implementation of TURN and STUN Server. Coturn before version 4.5.2 by default does not allow peers to connect and relay packets to loopback addresses in the range of 127.x.x.x. However, it was observed that when sending a CONNECT request with the XOR-PEER-ADDRESS value of 0.0.0.0, a successful response was received and subsequently, CONNECTIONBIND also received a successful response. Coturn then is able to relay packets to the loopback interface. Additionally, when coturn is listening on IPv6, which is default, the loopback interface can also be reached by making use of either [::1] or [::] as the peer address. By using the address 0.0.0.0 as the peer address, a malicious user will be able to relay packets to the loopback interface, unless --denied-peer-ip=0.0.0.0 (or similar) has been specified. Since the default configuration implies that loopback peers are not allowed, coturn administrators may choose to not set the denied-peer-ip setting. The issue patched in version 4.5.2. As a workaround the addresses in the address block 0.0.0.0/8, [::1] and [::] should be denied by default unless --allow-loopback-peers has been specified.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2020-26262?
CVE-2020-26262 is classified as a medium severity vulnerability.
How do I fix CVE-2020-26262?
To fix CVE-2020-26262, upgrade Coturn to version 4.5.2 or later.
Which software versions are affected by CVE-2020-26262?
CVE-2020-26262 affects Coturn versions prior to 4.5.2 as well as Fedora 32 and 33.
What type of vulnerability is CVE-2020-26262?
CVE-2020-26262 is a vulnerability that allows unauthorized connections to loopback addresses.
Can CVE-2020-26262 be exploited by external attackers?
Yes, CVE-2020-26262 can be exploited by attackers who can send crafted CONNECT requests.