First published: Thu Nov 14 2024(Updated: )
Incorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH). That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.
Credit: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
Affected Software | Affected Version | How to fix |
---|---|---|
PostgreSQL | >=12.0<12.21 | |
PostgreSQL | >=13.0<13.17 | |
PostgreSQL | >=14.0<14.14 | |
PostgreSQL | >=15.0<15.9 | |
PostgreSQL | >=16.0<16.5 | |
PostgreSQL | >=17.0<17.1 | |
debian/postgresql-13 | <=13.16-0+deb11u1 | 13.20-0+deb11u1 |
debian/postgresql-15 | 15.12-0+deb12u2 15.10-0+deb12u1 | |
debian/postgresql-17 | 17.4-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-10979 is considered a critical vulnerability due to the potential for arbitrary code execution.
To fix CVE-2024-10979, upgrade to PostgreSQL versions 13.18-0+deb11u1, 15.10-0+deb12u1, or 17.2-1.
CVE-2024-10979 allows unprivileged users to modify sensitive process environment variables in PostgreSQL PL/Perl.
Users of PostgreSQL versions earlier than 13.18, 15.10, or 17.2 who utilize PL/Perl may be affected by CVE-2024-10979.
Exploitation of CVE-2024-10979 can lead to arbitrary code execution, compromising the security of the database server.