Alerts This Week
Warning Icon 1 1,082
Alerts This Week
Warning Icon 1 1,082

Gentoo: GLSA-202411-07 High Severity: Pillow Arbitrary Code Execution

gentoo
Calendar Grey November 17, 2024
Dist Gentoo Esm H88
Gentoo Linux Security Advisory: GLSA 202411-08 tackles critical vulnerability in Requests library. Immediate patching advised.
A vulnerability has been discovered in Pillow, which may lead to arbitrary code execution.

Summary

A vulnerability has been discovered in Pillow. Please review the CVE identifier referenced below for details.

Topics%20covered

Topics Covered

security advisory security update high severity gentoo arbitrary code execution pillow

Resolution

All Pillow users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=dev-python/pillow-10.3.0"

References

[ 1 ] CVE-2024-28219 https://nvd.nist.gov/vuln/detail/CVE-2024-28219

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202411-07
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: High
Title: Pillow: Arbitrary code execution
Date: November 17, 2024
Bugs: #928391
ID: 202411-07

Topics%20covered

Topics Covered

security advisory security update high severity gentoo arbitrary code execution pillow

Synopsis

A vulnerability has been discovered in Pillow, which may lead to arbitrary code execution.

Background

The friendly PIL fork.

Get the latest News and Insights

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

Affected Packages

Package Vulnerable Unaffected ----------------- ------------ ------------ dev-python/pillow < 10.3.0 >= 10.3.0

Impact

Please review the referenced CVE identifier for details.

Workaround

There is no known workaround at this time.

Your message here