Overview 236 matches · 8 in Waratek scope · 2 protected · 3 exploited · 0 CISA KEV · 9 public PoC · 3 EPSS ≥ 0.5
236matches
8in Waratek scope3.4%
2protected0.8%
3exploited1.3%
0CISA KEV0.0%
9public PoC3.8%
3EPSS ≥ 0.51.3%
Protected by Waratek
2
0.8%
Rule in development
0
0.0%
Mitigation candidate
1
0.4%
No exploit published
5
2.1%
Outside Waratek scope
7
3.0%
Not applicable
221
93.6%
Withdrawn CVE
0
0.0%
blocked by ARMR today
2
0.8%
partly blocked
0
0.0%
not blocked
234
99.2%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 60 / year
19991
Not applicable1
Low1
not blocked1
No public exploit1
20000
20013
Not applicable3
High2
Medium1
not blocked3
Working exploit published1
No public exploit2
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
20097
Not applicable7
High1
Medium6
not blocked7
Working exploit published1
No public exploit6
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
Not applicable12
Critical1
High7
Medium4
not blocked12
Forecast only1
No public exploit11
201810
Outside Waratek scope1
Not applicable9
Critical2
High7
Medium1
not blocked10
Working exploit published1
No public exploit9
201912
Not applicable12
Critical2
High7
Medium2
Low1
not blocked12
Exploited1
No public exploit11
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
202211
Protected by Waratek1
No exploit published2
Outside Waratek scope2
Not applicable6
Critical3
High4
Medium4
blocked by ARMR today1
not blocked10
Exploited1
Proof of concept only1
No public exploit9
20239
Not applicable9
High3
Medium5
Low1
not blocked9
No public exploit9
202410
Mitigation candidate1
Not applicable9
Critical1
High5
Medium3
Low1
not blocked10
Exploited1
No public exploit9
20251
No exploit published1
High1
not blocked1
No public exploit1
202660
No exploit published2
Not applicable58
High33
Medium24
Low3
not blocked60
Proof of concept only1
No public exploit59
1999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2007-3278 | Medium | 2007-06-19 | Not applicable | No public exploit | PostgreSQL 8.1 and probably later versions, when local trust authentication is enabled and the Database Link library (dblink) is installed, allows remote attackers to access arbitrary accounts and execute arbitrary SQL queries via a dblink host parameter that proxies the connection from 127.0.0.1. |
| CVE-2007-2138 | Medium | 2007-04-24 | Not applicable | No public exploit | Untrusted search path vulnerability in PostgreSQL before 7.3.19, 7.4.x before 7.4.17, 8.0.x before 8.0.13, 8.1.x before 8.1.9, and 8.2.x before 8.2.4 allows remote authenticated users, when permitted to call a SECURITY DEFINER function, to gain the privileges of the function owner, related to "search_path settings." |
| CVE-2007-0556 | Medium | 2007-02-06 | Not applicable | No public exploit | The query planner in PostgreSQL before 8.0.11, 8.1 before 8.1.7, and 8.2 before 8.2.2 does not verify that a table is compatible with a "previously made query plan," which allows remote authenticated users to cause a denial of service (server crash) and possibly access database content via an "ALTER COLUMN TYPE" SQL statement, which can be leveraged to read arbitrary memory from the server. |
| CVE-2007-0555 | High | 2007-02-06 | Not applicable | No public exploit | PostgreSQL 7.3 before 7.3.13, 7.4 before 7.4.16, 8.0 before 8.0.11, 8.1 before 8.1.7, and 8.2 before 8.2.2 allows attackers to disable certain checks for the data types of SQL function arguments, which allows remote authenticated users to cause a denial of service (server crash) and possibly access database content. |
| CVE-2006-5542 | Medium | 2006-10-26 | Not applicable | No public exploit | backend/tcop/postgres.c in PostgreSQL 8.1.x before 8.1.5 allows remote authenticated users to cause a denial of service (daemon crash) related to duration logging of V3-protocol Execute messages for (1) COMMIT and (2) ROLLBACK SQL statements. |
| CVE-2006-5541 | Medium | 2006-10-26 | Not applicable | No public exploit | backend/parser/parse_coerce.c in PostgreSQL 7.4.1 through 7.4.14, 8.0.x before 8.0.9, and 8.1.x before 8.1.5 allows remote authenticated users to cause a denial of service (daemon crash) via a coercion of an unknown element to ANYARRAY. |
| CVE-2006-5540 | Medium | 2006-10-26 | Not applicable | No public exploit | backend/parser/analyze.c in PostgreSQL 8.1.x before 8.1.5 allows remote authenticated users to cause a denial of service (daemon crash) via certain aggregate functions in an UPDATE statement, which are not properly handled during a "MIN/MAX index optimization." |
| CVE-2006-2314 | High | 2006-05-24 | Not applicable | No public exploit | PostgreSQL 8.1.x before 8.1.4, 8.0.x before 8.0.8, 7.4.x before 7.4.13, 7.3.x before 7.3.15, and earlier versions allows context-dependent attackers to bypass SQL injection protection methods in applications that use multibyte encodings that allow the "\" (backslash) byte 0x5c to be the trailing byte of a multibyte character, such as SJIS, BIG5, GBK, GB18030, and UHC, which cannot be handled correctly by a client that does not understand multibyte encodings, aka a second variant of "Encoding-Based SQL Injection." NOTE: it could be argued that this is a class of issue related to interaction errors between the client and PostgreSQL, but a CVE has been assigned since PostgreSQL is treating this as a preventative measure against this class of problem. |
| CVE-2006-2313 | High | 2006-05-24 | Not applicable | No public exploit | PostgreSQL 8.1.x before 8.1.4, 8.0.x before 8.0.8, 7.4.x before 7.4.13, 7.3.x before 7.3.15, and earlier versions allows context-dependent attackers to bypass SQL injection protection methods in applications via invalid encodings of multibyte characters, aka one variant of "Encoding-Based SQL Injection." |
| CVE-2006-0678 | Low | 2006-02-14 | Not applicable | No public exploit | PostgreSQL 7.3.x before 7.3.14, 7.4.x before 7.4.12, 8.0.x before 8.0.7, and 8.1.x before 8.1.3, when compiled with Asserts enabled, allows local users to cause a denial of service (server crash) via a crafted SET SESSION AUTHORIZATION command, a different vulnerability than CVE-2006-0553. |
| CVE-2006-0553 | Medium | 2006-02-14 | Not applicable | No public exploit | PostgreSQL 8.1.0 through 8.1.2 allows authenticated database users to gain additional privileges via "knowledge of the backend protocol" using a crafted SET ROLE to other database users, a different vulnerability than CVE-2006-0678. |
| CVE-2006-0105 | Medium | 2006-01-10 | Not applicable | No public exploit | PostgreSQL 8.0.x before 8.0.6 and 8.1.x before 8.1.2, when running on Windows, allows remote attackers to cause a denial of service (postmaster exit and no new connections) via a large number of simultaneous connection requests. |
| CVE-2005-1410 | Low | 2005-05-03 | Not applicable | No public exploit | The tsearch2 module in PostgreSQL 7.4 through 8.0.x declares the (1) dex_init, (2) snb_en_init, (3) snb_ru_init, (4) spell_init, and (5) syn_init functions as "internal" even when they do not take an internal argument, which allows attackers to cause a denial of service (application crash) and possibly have other impacts via SQL commands that call other functions that accept internal arguments. |
| CVE-2005-1409 | High | 2005-05-03 | Not applicable | No public exploit | PostgreSQL 7.3.x through 8.0.x gives public EXECUTE access to certain character conversion functions, which allows unprivileged users to call those functions with malicious values, with unknown impact, aka the "Character conversion vulnerability." |
| CVE-2005-0247 | Medium | 2005-05-02 | Not applicable | No public exploit | Multiple buffer overflows in gram.y for PostgreSQL 8.0.1 and earlier may allow attackers to execute arbitrary code via (1) a large number of variables in a SQL statement being handled by the read_sql_construct function, (2) a large number of INTO variables in a SELECT statement being handled by the make_select_stmt function, (3) a large number of arbitrary variables in a SELECT statement being handled by the make_select_stmt function, and (4) a large number of INTO variables in a FETCH statement being handled by the make_fetch_stmt function, a different set of vulnerabilities than CVE-2005-0245. |
| CVE-2005-0246 | Medium | 2005-05-02 | Not applicable | No public exploit | The intagg contrib module for PostgreSQL 8.0.0 and earlier allows attackers to cause a denial of service (crash) via crafted arrays. |
| CVE-2005-0244 | Medium | 2005-05-02 | Not applicable | No public exploit | PostgreSQL 8.0.0 and earlier allows local users to bypass the EXECUTE permission check for functions by using the CREATE AGGREGATE command. |
| CVE-2005-0227 | Medium | 2005-05-02 | Not applicable | No public exploit | PostgreSQL (pgsql) 7.4.x, 7.2.x, and other versions allows local users to load arbitrary shared libraries and execute code via the LOAD extension. |
| CVE-2004-0977 | Low | 2005-02-09 | Not applicable | No public exploit | The make_oidjoins_check script in PostgreSQL 7.4.5 and earlier allows local users to overwrite files via a symlink attack on temporary files. |
| 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-2001-1090 | High | 2001-09-10 | Not applicable | No public exploit | nss_postgresql 0.6.1 and before allows a remote attacker to execute arbitrary SQL queries by inserting SQL code into an HTTP request. |
| CVE-2001-1089 | High | 2001-09-10 | Not applicable | No public exploit | libnss-pgsql in nss-pgsql 0.9.0 and earlier allows remote attackers to execute arbitrary SQL queries by inserting SQL code into an HTTP request. |
| 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. |