WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Vendor postgresql✕
Overview 215 matches · 9 in Waratek scope · 2 protected · 3 exploited · 0 CISA KEV · 9 public PoC · 3 EPSS ≥ 0.5
215matches 9in Waratek scope4.2% 2protected0.9% 3exploited1.4% 0CISA KEV0.0% 9public PoC4.2% 3EPSS ≥ 0.51.4%
Protected by Waratek 2 0.9% Rule in development 0 0.0% Mitigation candidate 1 0.5% No exploit published 6 2.8% Outside Waratek scope 7 3.3% Not applicable 199 92.6% Withdrawn CVE 0 0.0%
Critical 10 4.7% High 101 47.0% Medium 93 43.3% Low 11 5.1% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 2 0.9% partly blocked 0 0.0% not blocked 213 99.1% not established 0 0.0% unrecorded 0 0.0%
Exploited 3 1.4% Working exploit published 7 3.3% Proof of concept only 2 0.9% Forecast only 2 0.9% No public exploit 201 93.5%
split by peak 46 / year
Not applicable: 199Outside Waratek scope: 7No exploit published: 6Mitigation candidate: 1Protected by Waratek: 2 Low: 11Medium: 93High: 101Critical: 10 not blocked: 213blocked by ARMR today: 2 No public exploit: 201Forecast only: 2Proof of concept only: 2Working exploit published: 7Exploited: 3
19991 Not applicable1 Low1 not blocked1 No public exploit1 20000 20011 Not applicable1 Medium1 not blocked1 Working exploit published1 20024 Not applicable4 High3 Medium1 not blocked4 No public exploit4 20037 Not applicable7 High4 Medium3 not blocked7 No public exploit7 20041 Not applicable1 Medium1 not blocked1 No public exploit1 20058 Not applicable8 High2 Medium4 Low2 not blocked8 Working exploit published1 No public exploit7 20068 Not applicable8 High2 Medium5 Low1 not blocked8 No public exploit8 20076 Not applicable6 High3 Medium3 not blocked6 Working exploit published1 No public exploit5 20085 Not applicable5 High1 Medium4 not blocked5 No public exploit5 20096 Not applicable6 Medium6 not blocked6 Working exploit published1 No public exploit5 20107 Not applicable7 High2 Medium4 Low1 not blocked7 Working exploit published2 No public exploit5 20112 Not applicable2 Medium2 not blocked2 No public exploit2 20128 Protected by Waratek1 Not applicable7 High1 Medium7 blocked by ARMR today1 not blocked7 No public exploit8 20136 Not applicable6 High3 Medium3 not blocked6 Forecast only1 No public exploit5 20149 Not applicable9 Medium9 not blocked9 No public exploit9 20153 Not applicable3 Medium3 not blocked3 No public exploit3 20166 Not applicable6 Critical1 High5 not blocked6 No public exploit6 201712 No exploit published1 Not applicable11 Critical1 High6 Medium5 not blocked12 Forecast only1 No public exploit11 201810 Outside Waratek scope1 Not applicable9 Critical2 High7 Medium1 not blocked10 Working exploit published1 No public exploit9 201911 Not applicable11 Critical2 High6 Medium2 Low1 not blocked11 Exploited1 No public exploit10 202013 Outside Waratek scope2 Not applicable11 Critical1 High10 Medium2 not blocked13 No public exploit13 20217 Outside Waratek scope2 Not applicable5 High3 Medium4 not blocked7 No public exploit7 202210 Protected by Waratek1 No exploit published2 Outside Waratek scope2 Not applicable5 Critical2 High4 Medium4 blocked by ARMR today1 not blocked9 Exploited1 Proof of concept only1 No public exploit8 20239 Not applicable9 High3 Medium5 Low1 not blocked9 No public exploit9 20248 Mitigation candidate1 Not applicable7 Critical1 High3 Medium3 Low1 not blocked8 Exploited1 No public exploit7 20251 No exploit published1 High1 not blocked1 No public exploit1 202646 No exploit published2 Not applicable44 High32 Medium11 Low3 not blocked46 Proof of concept only1 No public exploit45
1999200220052008201120142017202020232026
215 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 3 of 3 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2005-0245 High 2005-02-01 Not applicable Working exploit published Buffer overflow in gram.y for PostgreSQL 8.0.0 and earlier may allow attackers to execute arbitrary code via a large number of arguments to a refcursor function (gram.y), which leads to a heap-based buffer overflow, a different vulnerability than CVE-2005-0247.
CVE-2004-0547 Medium 2004-08-06 Not applicable No public exploit Buffer overflow in the ODBC driver for PostgreSQL before 7.2.1 allows remote attackers to cause a denial of service (crash).
CVE-2003-0901 High 2003-11-03 Not applicable No public exploit Buffer overflow in to_ascii for PostgreSQL 7.2.x, and 7.3.x before 7.3.4, allows remote attackers to execute arbitrary code.
CVE-2002-1402 Medium 2003-01-17 Not applicable No public exploit Buffer overflows in the (1) TZ and (2) SET TIME ZONE enivronment variables for PostgreSQL 7.2.1 and earlier allow local users to cause a denial of service and possibly execute arbitrary code.
CVE-2002-1401 Medium 2003-01-17 Not applicable No public exploit Buffer overflows in (1) circle_poly, (2) path_encode and (3) path_add (also incorrectly identified as path_addr) for PostgreSQL 7.2.3 and earlier allow attackers to cause a denial of service and possibly execute arbitrary code, possibly as a result of an integer overflow.
CVE-2002-1400 High 2003-01-17 Not applicable No public exploit Heap-based buffer overflow in the repeat() function for PostgreSQL before 7.2.2 allows attackers to execute arbitrary code by causing repeat() to generate a large string.
CVE-2002-1399 High 2003-01-17 Not applicable No public exploit Unknown vulnerability in cash_out and possibly other functions in PostgreSQL 7.2.1 and earlier, and possibly later versions before 7.2.3, with unknown impact, based on an invalid integer input which is processed as a different data type, as demonstrated using cash_out(2).
CVE-2002-1398 Medium 2003-01-17 Not applicable No public exploit Buffer overflow in the date parser for PostgreSQL before 7.2.2 allows attackers to cause a denial of service and possibly execute arbitrary code via a long date string, aka a vulnerability "in handling long datetime input."
CVE-2002-1397 High 2003-01-17 Not applicable No public exploit Vulnerability in the cash_words() function for PostgreSQL 7.2 and earlier allows local users to cause a denial of service and possibly execute arbitrary code via a large negative argument, possibly triggering an integer signedness error or buffer overflow.
CVE-2002-1657 High 2002-12-31 Not applicable No public exploit PostgreSQL uses the username for a salt when generating passwords, which makes it easier for remote attackers to guess passwords via a brute force attack.
CVE-2002-1642 High 2002-10-03 Not applicable No public exploit PostgreSQL 7.2.1 and 7.2.2 allows local users to delete transaction log (pg_clog) data and cause a denial of service (data loss) via the VACUUM command.
CVE-2002-0972 Medium 2002-09-24 Not applicable No public exploit Buffer overflows in PostgreSQL 7.2 allow attackers to cause a denial of service and possibly execute arbitrary code via long arguments to the functions (1) lpad or (2) rpad.
CVE-2002-0802 High 2002-08-12 Not applicable No public exploit The multibyte support in PostgreSQL 6.5.x with SQL_ASCII encoding consumes an extra character when processing a character that cannot be converted, which could remove an escape character from the query and make the application subject to SQL injection attacks.
CVE-2000-1199 Medium 2001-08-31 Not applicable Working exploit published PostgreSQL stores usernames and passwords in plaintext in (1) pg_shadow and (2) pg_pwd, which allows attackers with sufficient privileges to gain access to databases.
CVE-1999-0862 Low 1999-12-02 Not applicable No public exploit Insecure directory permissions in RPM distribution for PostgreSQL allows local users to gain privileges by reading a plaintext password file.
‹ prev page 3 of 3 next ›