Summary: | <media-libs/libjpeg-turbo-2.0.3: several integer overflows and subsequent segfaults when attempting to compress/decompress gigapixel images (CVE-2019-2201) | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | GLSAMaker/CVETool Bot <glsamaker> |
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | graphics+disabled, nobrowser, sam |
Priority: | Normal | Flags: | stable-bot:
sanity-check+
|
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://source.android.com/security/bulletin/2019-11-01 | ||
Whiteboard: | A2 [glsa+ cve] | ||
Package list: |
media-libs/libjpeg-turbo-2.0.3
|
Runtime testing required: | --- |
Description
GLSAMaker/CVETool Bot
2019-11-11 16:32:00 UTC
x86 stable sparc stable ppc64 stable arm64 stable ppc stable amd64 stable hppa stable ia64 stable alpha stable arm stable I'd like to point out that in the announcement of this bug on oss-security [1], it says: > integer overflow and subsequent heap corruption in libjpeg-turbo *2.0.3 and earlier* (emph mine) If that is right, a simple bump to 2.0.3 would not have fixed it in our distro. I tried to follow the link to NIST, but there it is stated in term of Android versions only, and my eyes glaze over. Sorry, please someone follow up. [1] https://www.openwall.com/lists/oss-security/2019/11/11/1 @ Ian: This bug is about CVE-2019-2201 which is linked to https://github.com/libjpeg-turbo/libjpeg-turbo/commit/2a9e3bd7430cfda1bc812d139e0609c6aca0b884 and this commit is present in v2.0.3. I guess the CVE text is not correct. If you have any other information, please share. New GLSA request filed. This issue was resolved and addressed in GLSA 202003-23 at https://security.gentoo.org/glsa/202003-23 by GLSA coordinator Thomas Deutschmann (whissi). *** Bug 727910 has been marked as a duplicate of this bug. *** |