Alerts This Week
Warning Icon 1 714
Alerts This Week
Warning Icon 1 714

Gentoo: GLSA-202009-04 Low Severity: Qt GUI Buffer Overflow Detected

gentoo
Calendar Grey September 13, 2020
Dist Gentoo Esm H88
A vulnerability in the Qt graphical user interface on Gentoo Linux is identified, posing a buffer overflow risk. Users should upgrade to mitigate threats. More details are available.
Qt GUI has a buffer overflow with unspecified impact.

Summary

It was discovered that Qt GUI's XBM parser did not properly handle X BitMap files.

Topics%20covered

Topics Covered

security advisory Gentoo buffer overflow low severity Qt GUI

Resolution

All Qt GUI users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-qt/qtgui-5.14.2-r1"

References

[ 1 ] CVE-2020-17507 https://nvd.nist.gov/vuln/detail/CVE-2020-17507

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202009-04
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
low
Lowest
Low
Medium
High
Critical

Severity: Low
Title: Qt GUI: Buffer overflow
Date: September 13, 2020
Bugs: #736924
ID: 202009-04

Topics%20covered

Topics Covered

security advisory Gentoo buffer overflow low severity Qt GUI

Synopsis

Qt GUI has a buffer overflow with unspecified impact.

Background

The GUI module and platform plugins for the Qt5 framework.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-qt/qtgui < 5.14.2-r1 >= 5.14.2-r1

Impact

===== Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Your message here