WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Product postgresql✕
Overview 11 matches · 2 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 0 public PoC · 1 EPSS ≥ 0.5
11matches 2in Waratek scope18.2% 0protected0.0% 1exploited9.1% 0CISA KEV0.0% 0public PoC0.0% 1EPSS ≥ 0.59.1%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 1 9.1% No exploit published 1 9.1% Outside Waratek scope 1 9.1% Not applicable 8 72.7% Withdrawn CVE 0 0.0%
Critical 11 100.0% High 0 0.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 11 100.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 1 9.1% Working exploit published 0 0.0% Proof of concept only 1 9.1% Forecast only 1 9.1% No public exploit 8 72.7%
split by peak 3 / year
Not applicable: 8Outside Waratek scope: 1No exploit published: 1Mitigation candidate: 1 Critical: 11 not blocked: 11 No public exploit: 8Forecast only: 1Proof of concept only: 1Exploited: 1
20161 Not applicable1 Critical1 not blocked1 No public exploit1 20171 Not applicable1 Critical1 not blocked1 Forecast only1 20182 Not applicable2 Critical2 not blocked2 No public exploit2 20192 Not applicable2 Critical2 not blocked2 No public exploit2 20201 Not applicable1 Critical1 not blocked1 No public exploit1 20210 20223 No exploit published1 Outside Waratek scope1 Not applicable1 Critical3 not blocked3 Proof of concept only1 No public exploit2 20230 20241 Mitigation candidate1 Critical1 not blocked1 Exploited1
201620172018201920202021202220232024
11 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2024-1597 Critical 2024-02-19 Mitigation candidate Exploited pgjdbc, the PostgreSQL JDBC Driver, allows attacker to inject SQL if using PreferQueryMode=SIMPLE. Note this is not the default. In the default mode there is no vulnerability. A placeholder for a numeric value must be immediately preceded by a minus. There must be a second placeholder for a string value after the first placeholder; both must be on the same line. By constructing a matching string payload, the attacker can inject SQL to alter the query,bypassing the protections that parameterized queries bring against SQL Injection attacks. Versions before 42.7.2, 42.6.1, 42.5.5, 42.4.4, 42.3.9, and 42.2.28 are affected.
CVE-2022-35942 Critical 2022-08-12 Not applicable No public exploit Improper input validation on the `contains` LoopBack filter may allow for arbitrary SQL injection. When the extended filter property `contains` is permitted to be interpreted by the Postgres connector, it is possible to inject arbitrary SQL which may affect the confidentiality and integrity of data stored on the connected database. A patch was released in version 5.5.1. This affects users who does any of the following: - Connect to the database via the DataSource with `allowExtendedProperties: true` setting OR - Uses the connector's CRUD methods directly OR - Uses the connector's other methods to interpret the LoopBack filter. Users who are unable to upgrade should do the following if applicable: - Remove `allowExtendedProperties: true` DataSource setting - Add `allowExtendedProperties: false` DataSource setting - When passing directly to the connector functions, manually sanitize the user input for the `contains` LoopBack filter beforehand.
CVE-2022-26520 Critical 2022-03-10 No exploit published No public exploit In pgjdbc before 42.3.3, an attacker (who controls the jdbc URL or properties) can call java.util.logging.FileHandler to write to arbitrary files through the loggerFile and loggerLevel connection properties. An example situation is that an attacker could create an executable JSP file under a Tomcat web root. NOTE: the vendor's position is that there is no pgjdbc vulnerability; instead, it is a vulnerability for any application to use the pgjdbc driver with untrusted connection properties
CVE-2022-21724 Critical 2022-02-02 Outside Waratek scope Proof of concept only pgjdbc is the offical PostgreSQL JDBC Driver. A security hole was found in the jdbc driver for postgresql database while doing security research. The system using the postgresql library will be attacked when attacker control the jdbc url or properties. pgjdbc instantiates plugin instances based on class names provided via `authenticationPluginClassName`, `sslhostnameverifier`, `socketFactory`, `sslfactory`, `sslpasswordcallback` connection properties. However, the driver did not verify if the class implements the expected interface before instantiating the class. This can lead to code execution loaded via arbitrary classes. Users using plugins are advised to upgrade. There are no known workarounds for this issue.
CVE-2015-0244 Critical 2020-01-27 Not applicable No public exploit PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 does not properly handle errors while reading a protocol message, which allows remote attackers to conduct SQL injection attacks via crafted binary data in a parameter and causing an error, which triggers the loss of synchronization and part of the protocol message to be treated as a new message, as demonstrated by causing a timeout or query cancellation.
CVE-2015-3166 Critical 2019-11-20 Not applicable No public exploit The snprintf implementation in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 does not properly handle system-call errors, which allows attackers to obtain sensitive information or have other unspecified impact via unknown vectors, as demonstrated by an out-of-memory error.
CVE-2019-10211 Critical 2019-10-29 Not applicable No public exploit Postgresql Windows installer before versions 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24 is vulnerable via bundled OpenSSL executing code from unprotected directory.
CVE-2018-16850 Critical 2018-11-13 Not applicable No public exploit postgresql 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-1115 Critical 2018-05-10 Not applicable No public exploit postgresql 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-2017-7546 Critical 2017-08-16 Not applicable Forecast only PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote attackers to gain access to database accounts with an empty password.
CVE-2016-3065 Critical 2016-04-11 Not applicable No public exploit The (1) brin_page_type and (2) brin_metapage_info functions in the pageinspect extension in PostgreSQL before 9.5.x before 9.5.2 allows attackers to bypass intended access restrictions and consequently obtain sensitive server memory information or cause a denial of service (server crash) via a crafted bytea value in a BRIN index page.