Alerts This Week
Warning Icon 1 1,149
Alerts This Week
Warning Icon 1 1,149

Gentoo: GLSA-202409-17 normal: VLC multiple code execution risks

gentoo
Calendar Grey September 22, 2024
Dist Gentoo Esm H88
Several security flaws in VLC may allow unauthorized code execution. Update to version 3.0.20 to reduce these threats.
Multiple vulnerabilities have been discovered in VLC, the worst of which could result in arbitrary code execution.

Summary

Multiple vulnerabilities have been discovered in VLC. Please review the CVE identifiers referenced below for details.

Topics%20covered

Topics Covered

security advisory Gentoo arbitrary code media player normal severity

Resolution

All VLC users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=media-video/vlc-3.0.20"

References

[ 1 ] CVE-2022-41325 https://nvd.nist.gov/vuln/detail/CVE-2022-41325

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202409-17
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: Normal
Title: VLC: Multiple Vulnerabilities
Date: September 22, 2024
Bugs: #788226, #883943, #917274
ID: 202409-17

Topics%20covered

Topics Covered

security advisory Gentoo arbitrary code media player normal severity

Synopsis

Multiple vulnerabilities have been discovered in VLC, the worst of which could result in arbitrary code execution.

Background

VLC is a cross-platform media player and streaming server.

Get the latest News and Insights

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

Affected Packages

Package Vulnerable Unaffected --------------- ------------ ------------ media-video/vlc < 3.0.20 >= 3.0.20

Impact

Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Your message here