Skip to content

Product

azure linux postgresql17 vulnerabilities

47 published CVES affecting azure linux postgresql17, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
47
Critical
0
High
36
Medium
10
Low
1
Unscored
0
CISA KEV
0

Latest azure linux postgresql17 CVEs

Newest publication first · page 2 of 2

  1. HighCVSS 8.8 EPSS 0.64%

    Uncaught exceptions in PostgreSQL plperl allow an object creator to cause use of a stale sigjmp_buf, via a tied Perl object, or a Perl object whose overloaded conversion throws while plperl is handling another error. We have not ruled out arbitrary code execution on some platform...

  2. HighCVSS 8.0 EPSS 0.38%

    SQL injection in PostgreSQL reindexdb allows an object creator to execute arbitrary SQL as the database user running reindexdb, via a crafted index name embedded in the parallel catalog query for --jobs with --index. Within major versions 17-18, minor versions before PostgreSQL 1...

  3. MediumCVSS 4.3 EPSS 0.30%

    Improper null termination in PostgreSQL array element assignment allows a database user to disclose server memory, via changing the final byte of a fixed-length name value to a nonzero byte and passing it to code that treats the value as a C string. Versions before PostgreSQL 18....

  4. HighCVSS 7.2 EPSS 0.53%

    Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege to dlopen any file visible to the operating system account running the server, via the choice of logical decoding plugin. This in turn runs arbitrary code as that account. Ve...

  5. HighCVSS 8.8 EPSS 0.42%

    Type confusion with PostgreSQL "internal" data type arguments allows any user to execute arbitrary code as the operating system user running the database, via calls to functions with that argument type. Type "internal" represents a class of mutually-incompatible data structures n...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.