CVE-2024-10979

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.

Weakness

One or more system settings or configuration elements can be externally controlled by a user.

Affected Software

Potential Mitigations

• Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
• Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/13.html
• https://cwe.mitre.org/data/definitions/146.html
• https://cwe.mitre.org/data/definitions/176.html
• https://cwe.mitre.org/data/definitions/203.html
• https://cwe.mitre.org/data/definitions/270.html
• https://cwe.mitre.org/data/definitions/271.html
• https://cwe.mitre.org/data/definitions/579.html
• https://cwe.mitre.org/data/definitions/69.html
• https://cwe.mitre.org/data/definitions/76.html
• https://cwe.mitre.org/data/definitions/77.html

References

• https://www.postgresql.org/support/security/CVE-2024-10979/
• https://github.com/fmora50591/postgresql-env-vuln/blob/main/README.md
• https://security.netapp.com/advisory/ntap-20250110-0003/