Vulnerability from bitnami_vulndb
Published
2024-11-16 07:16
Modified
2025-11-06 13:25
Summary
PostgreSQL PL/Perl environment variable changes execute arbitrary code
Details

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.

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "postgresql",
        "purl": "pkg:bitnami/postgresql"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "13.17.0"
            },
            {
              "introduced": "14.0.0"
            },
            {
              "fixed": "14.14.0"
            },
            {
              "introduced": "15.0.0"
            },
            {
              "fixed": "15.9.0"
            },
            {
              "introduced": "16.0.0"
            },
            {
              "fixed": "16.5.0"
            },
            {
              "introduced": "17.0.0"
            },
            {
              "fixed": "17.1.0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-10979"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*"
    ],
    "severity": "High"
  },
  "details": "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.",
  "id": "BIT-postgresql-2024-10979",
  "modified": "2025-11-06T13:25:46.476Z",
  "published": "2024-11-16T07:16:38.797Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.postgresql.org/support/security/CVE-2024-10979/"
    },
    {
      "type": "WEB",
      "url": "https://github.com/fmora50591/postgresql-env-vuln/blob/main/README.md"
    },
    {
      "type": "WEB",
      "url": "https://security.netapp.com/advisory/ntap-20250110-0003/"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10979"
    },
    {
      "type": "WEB",
      "url": "https://lists.debian.org/debian-lts-announce/2024/11/msg00011.html"
    }
  ],
  "schema_version": "1.5.0",
  "summary": "PostgreSQL PL/Perl environment variable changes execute arbitrary code"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.