CVE-2005-0245: postgresql

EPSS trend

Probability

14.47%

Chance of exploitation in the next 30 days

Percentile

97%

Versus all other CVEs

30-day change

0.00 pp

From 14.47% on 20-09-2026

20-09-202620-10-2026

EPSS score

14.47%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

4 found

referenceUnverified
Exploit Reference (archives.postgresql.org)
Maturity: unknown
referenceUnverified
Exploit Reference (secunia.com)
Maturity: unknown
referenceUnverified
Exploit Reference (debian.org)
Maturity: unknown

Show all 4 exploits

exploit-databasedoslinuxVerified
PostgreSQL 7.x - Multiple Vulnerabilities
Maturity: poc

References

13 links

exchange.xforce.ibmcloud.com/vulnerabilities/19188VDB EntryX Refsource XFThird Party Advisory
archives.postgresql.org/pgsql-committers/2005-02/msg00049.phpMailing ListX Refsource MLISTVendor Advisory
www.mandriva.com/security/advisories?name=MDKSA-2005:040Vendor AdvisoryX Refsource MANDRAKEBroken Link
marc.info?l=bugtraq&m=110806034116082&w=2Mailing ListX Refsource BUGTRAQIssue TrackingThird Party Advisory
oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10175VDB EntrySignatureX Refsource OVALThird Party Advisory
archives.postgresql.org/pgsql-patches/2005-01/msg00216.phpMailing ListX Refsource MLISTExploitVendor Advisory
www.redhat.com/support/errata/RHSA-2005-138.htmlVendor AdvisoryX Refsource REDHATPatch
secunia.com/advisories/12948Third Party AdvisoryX Refsource SECUNIAExploitPatchVendor Advisory
www.redhat.com/support/errata/RHSA-2005-150.htmlVendor AdvisoryX Refsource REDHATPatch
archives.postgresql.org/pgsql-committers/2005-01/msg00298.phpMailing ListX Refsource MLISTVendor Advisory

Show all 13 references

www.securityfocus.com/bid/12417VDB EntryX Refsource BIDThird Party Advisory
www.debian.org/security/2005/dsa-683Vendor AdvisoryX Refsource DEBIANExploit
www.novell.com/linux/security/advisories/2005_36_sudo.htmlVendor AdvisoryX Refsource SUSEBroken Link

Related vulnerabilities

CVE-2018-16850alpinepostgresql+395.15%7y ago13-11-2018 15:00postgresql before versions 11.1, 10.6 is vulnerable to a to SQL injection in pg_upgrade and pg_dump via CREATE TRIGGER ... REFERENCING. Using a purpose-crafted trigger definition, an attacker can cause arbitrary SQL statements to run, with superuser privileges.CVE-2018-1053alpinepostgresql+390.48%8y ago09-02-2018 14:00In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.CVE-2018-1115alpinepostgresql+133.83%8y ago10-05-2018 19:00postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could exploit this to force log rotation.CVE-2018-1058alpinepostgresql+3513.10%8y ago02-03-2018 15:00A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users. An attacker with a user account could use this flaw to execute code with the permissions of superuser in the database. Versions 9.3 through 10 are affected.CVE-2018-10915alpinepostgresql+415.09%8y ago09-08-2018 20:00A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with "host" or "hostaddr" connection parameters from untrusted input, attackers could bypass client-side connection security features, obtain access to higher privileged connections or potentially cause other impact through SQL injection, by causing the PQescape() functions to malfunction. Postgresql versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 are affected.CVE-2018-10925alpinepostgresql+82.24%8y ago09-08-2018 21:00It was discovered that PostgreSQL versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 failed to properly check authorization on certain statements involved with "INSERT ... ON CONFLICT DO UPDATE". An attacker with "CREATE TABLE" privileges could exploit this to read arbitrary bytes server memory. If the attacker also had certain "INSERT" and limited "UPDATE" privileges to a particular table, they could exploit this to update other columns in the same table.

All vulnerabilities inpostgresql

CVE-2005-0245: postgresql

Vulnerability summary

Advisory lineage

Timeline

Description

CVSS metrics

EPSS trend

Known exploited

Public exploits

Weaknesses

Affected systems

References