First published: Mon Jun 22 2020(Updated: )
In FreeRDP before version 2.1.2, there is an out of bounds read in TrioParse. Logging might bypass string length checks due to an integer overflow. This is fixed in version 2.1.2.
Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
FreeRDP FreeRDP | <2.1.2 | |
Fedoraproject Fedora | =31 | |
Fedoraproject Fedora | =32 | |
openSUSE Leap | =15.1 | |
Canonical Ubuntu Linux | =18.04 | |
Canonical Ubuntu Linux | =20.04 | |
Debian Debian Linux | =10.0 | |
debian/freerdp2 | 2.3.0+dfsg1-2+deb11u1 2.10.0+dfsg1-1 2.11.7+dfsg1-4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-4030 is a vulnerability in FreeRDP before version 2.1.2 that allows an out of bounds read in TrioParse, which can bypass string length checks.
The severity of CVE-2020-4030 is medium, with a severity value of 6.5.
CVE-2020-4030 affects FreeRDP versions before 2.1.2, allowing for an out of bounds read in TrioParse.
Yes, the vulnerability is fixed in FreeRDP version 2.1.2.
You can find more information about CVE-2020-4030 at the MITRE CVE database (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-4030), the FreeRDP security advisories on GitHub (https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-fjr5-97f5-qq98), and the FreeRDP website (http://www.freerdp.com/2020/06/22/2_1_2-released).