Strix
26.1K

CVE-2017-16612

UnknownEPSS 5.17%

Last modified

CVE-2017-16612 is a vulnerability of currently unknown severity. libXcursor before 1.1.15 has various integer overflows that could lead to heap buffer overflows when processing malicious cursors, e.g., with programs like GIMP. It is also possible that an attack vector exists against the related code in cursor/xcursor.c in Wayland through 1.14.0.. EPSS estimates a 5.17% chance of exploitation in the next 30 days.

Description

libXcursor before 1.1.15 has various integer overflows that could lead to heap buffer overflows when processing malicious cursors, e.g., with programs like GIMP. It is also possible that an attack vector exists against the related code in cursor/xcursor.c in Wayland through 1.14.0.

Metrics

EPSS Probability
5.17%

91.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
DebianDebian Linux8.0
DebianDebian Linux9.0
CanonicalUbuntu Linux14.04
CanonicalUbuntu Linux16.04
CanonicalUbuntu Linux17.04
CanonicalUbuntu Linux17.10
XLibxcursor<= 1.1.14

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-16612?
libXcursor before 1.1.15 has various integer overflows that could lead to heap buffer overflows when processing malicious cursors, e.g., with programs like GIMP. It is also possible that an attack vector exists against the related code in cursor/xcursor.c in Wayland through 1.14.0.
How severe is CVE-2017-16612?
Severity scoring for CVE-2017-16612 is pending analysis. The EPSS model estimates a 5.17% probability of exploitation in the next 30 days.
How do I fix CVE-2017-16612?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-16612?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST