CyberSecBulletin
CVE-2022-21724NVD status: Modified

Postgresql Jdbc Driver: Improper Initialization

Published Updated By the CyberSecBulletin desk

CVE-2022-21724 is a critical-severity improper initialization vulnerability in Postgresql Jdbc Driver from PostgreSQL, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 42.2.25, 42.3.2 as the first without the flaw, so updating Postgresql Jdbc Driver to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 3.09% chance of exploitation within 30 days, higher than 88% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Postgresql Jdbc Driver to 42.2.25 or 42.3.2, whichever matches your release line, or a later version.
  2. Update Quarkus to 2.7.2 or a later version.
  3. Read the advisory on github.com for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
PostgreSQLPostgresql Jdbc Driverbefore 42.2.25; 42.3.0 up to, but not including, 42.3.2; 42.3.242.2.25, 42.3.2
Fedora ProjectFedora35Not stated
QuarkusQuarkusbefore 2.7.22.7.2
DebianDebian Linux9.0; 10.0; 11.0Not stated

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.0HighCNA (github.com)
CVSS 3.19.8CriticalNVD
CVSS 2.07.5HighNVD

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Initialization

The product does not initialize or incorrectly initializes a resource.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable's type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed.
  • Identify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values.
  • Explicitly initialize all your variables and other data stores, either during declaration or just before the first usage.

More Improper Initialization vulnerabilities (CWE-665)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in Postgresql Jdbc Driver

All Postgresql Jdbc Driver vulnerabilities

Recent Improper Initialization vulnerabilities

Spotted an error? Tell us.