ubuntu-cve-2020-26262
Vulnerability from osv_ubuntu
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": [
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "coturn",
"binary_version": "4.5.0.3-1ubuntu0.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "coturn",
"purl": "pkg:deb/ubuntu/coturn@4.5.0.3-1ubuntu0.4?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.5.0.3-1ubuntu0.4"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.5.4-2",
"4.5.0.2-3",
"4.5.0.3-1",
"4.5.0.3-1build1",
"4.5.0.3-1ubuntu0.2",
"4.5.0.3-1ubuntu0.3"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "coturn",
"binary_version": "4.5.0.7-1ubuntu2.18.04.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "coturn",
"purl": "pkg:deb/ubuntu/coturn@4.5.0.7-1ubuntu2.18.04.3?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.5.0.7-1ubuntu2.18.04.3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.5.0.6-1ubuntu2",
"4.5.0.7-1ubuntu1",
"4.5.0.7-1ubuntu2",
"4.5.0.7-1ubuntu2.18.04.1",
"4.5.0.7-1ubuntu2.18.04.2"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "coturn",
"binary_version": "4.5.1.1-1.1ubuntu0.20.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "coturn",
"purl": "pkg:deb/ubuntu/coturn@4.5.1.1-1.1ubuntu0.20.04.2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.5.1.1-1.1ubuntu0.20.04.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.5.1.1-1.1build1",
"4.5.1.1-1.1build2",
"4.5.1.1-1.1ubuntu0.20.04.1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2020-26262",
"modified": "2025-09-08T16:46:23Z",
"published": "2021-01-11T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-26262"
},
{
"type": "REPORT",
"url": "https://github.com/coturn/coturn/security/advisories/GHSA-6g6j-r9rf-cm7p"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-4690-1"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-26262"
}
],
"related": [
"USN-4690-1"
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2020-26262"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.