ID CVE-2020-4067
Summary In coturn before version 4.5.1.3, there is an issue whereby STUN/TURN response buffer is not initialized properly. There is a leak of information between different client connections. One client (an attacker) could use their connection to intelligently query coturn to get interesting bytes in the padding bytes from the connection of another client. This has been fixed in 4.5.1.3.
References
Vulnerable Configurations
  • cpe:2.3:a:coturn_project:coturn:4.4.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.4.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.4.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.4.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coturn_project:coturn:4.5.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:coturn_project:coturn:4.5.1.2:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:10:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:10:*:*:*:*:*:*:*
CVSS
Base: 5.0
Impact:
Exploitability:
CWE CWE-665
CAPEC
  • Leveraging Race Conditions
    This attack targets a race condition occurring when multiple processes access and manipulate the same resource concurrently and the outcome of the execution depends on the particular order in which the access takes place. The attacker can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance a race condition can occur while accessing a file, the attacker can trick the system by replacing the original file with his version and cause the system to read the malicious file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions
    This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. The typical example is the file access. The attacker can leverage a file access race condition by "running the race", meaning that he would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the attacker could do something such as replace the file and cause an escalation of privilege.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
Last major update 29-06-2020 - 20:38
Published 29-06-2020 - 20:15
Last modified 09-07-2020 - 03:15
Back to Top