Alerts This Week
Warning Icon 1 727
Alerts This Week
Warning Icon 1 727

Gentoo: GLSA 202502-04 moderate: npm remote code execution vulnerability

gentoo
Calendar Grey January 17, 2025
Dist Gentoo Esm H88
The Gentoo GLSA 202501-04 highlights a critical vulnerability in curl, necessitating immediate action for all affected users.
A vulnerability has been discovered in pip, which could lead to arbitrary configuration options being injected.

Summary

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

Resolution

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

References

[ 1 ] CVE-2023-5752 https://nvd.nist.gov/vuln/detail/CVE-2023-5752

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202501-03
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: pip: arbitrary configuration injection
Date: January 17, 2025
Bugs: #918427
ID: 202501-03

Synopsis

A vulnerability has been discovered in pip, which could lead to arbitrary configuration options being injected.

Background

pip is a tool for installing and managing Python packages.

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/pip < 23.3 >= 23.3

Impact

When installing a package from a Mercurial VCS URL (ie "pip install hg+..."), the specified Mercurial revision could be used to inject arbitrary configuration options to the "hg clone" call (ie "--config"). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who aren't installing from Mercurial.

Workaround

There is no known workaround at this time.

Your message here