Evidence used
- No CISA KEV confirmation is currently recorded.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 2.23% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2022
CVE-2022-31197High confidence
SQL Injection in ResultSet.refreshRow() with malicious column names in pgjdbc
pgjdbc · pgjdbc
Official source article: GitHub GHSA-R38F-C4H4-HQQ2 ↗. Check the applicable product and release in the original source.
7.1HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 3 Nov 2025
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs pgjdbc pgjdbc and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
8 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | java-postgresql-jdbc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 42.4.2-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | java-postgresql-jdbc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 42.4.2-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.21v3.21 · community | java-postgresql-jdbc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 42.4.2-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Debian trixietrixie · source | libpgjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 42.4.1-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | libpgjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 42.4.1-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | libpgjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 42.4.1-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | libpgjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 42.4.1-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | libpgjava | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Open-source package ranges6 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavenorg.postgresql:postgresql | ECOSYSTEM: introduced 0; fixed 42.2.26 | 42.2.26 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.postgresql:postgresql | ECOSYSTEM: introduced 42.4.0; fixed 42.4.1 | 42.4.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.postgresql:postgresql | ECOSYSTEM: introduced 42.3.0; fixed 42.3.7 | 42.3.7 | OSV record ↗aggregator derived · 10 Sep 2026 |
| mavenorg.postgresql:postgresql | < 42.2.26 | 42.2.26 | GitHub advisory ↗upstream repository advisory · 4 Nov 2025 |
| mavenorg.postgresql:postgresql | >= 42.4.0, < 42.4.1 | 42.4.1 | GitHub advisory ↗upstream repository advisory · 4 Nov 2025 |
| mavenorg.postgresql:postgresql | >= 42.3.0, < 42.3.7 | 42.3.7 | GitHub advisory ↗upstream repository advisory · 4 Nov 2025 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2022-31197 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypostgresql: SQL Injection in ResultSet.refreshRow() with malicious column names
The vendor explicitly identifies these products as affected by this CVE.
- quarkus-jdbc-postgresql-deployment as a component of Red Hat build of Apicurio Registry 2
- jdbc-postgresql as a component of Red Hat Decision Manager 7
- autocorr-af (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-bg (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-ca (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-cs (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-da (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-de (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-en (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-es (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-fa (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-fi (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- Summary
- A flaw was found in PostgresQL. This flaw allows an attacker to benefit from a miss escaping character and leads to a SQL injection attack due to Java.sql.ResultRow.refreshRow() implementation from PGSQL.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 If the postgresql service is running, it will be automatically restarted after installing this update.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
PostgreSQL JDBC Driver (PgJDBC for short) allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. The PGJDBC implementation of the `java.sql.ResultRow.refreshRow()` method is not performing escaping of column names so a malicious column name that contains a statement terminator, e.g. `;`, could lead to SQL injection. This could lead to executing additional SQL commands as the application's JDBC user. User applications that do not invoke the `ResultSet.refreshRow()` method are not impacted. User application that do invoke that method are impacted if the underlying database that they are querying via their JDBC application may be under the control of an attacker. The attack requires the attacker to trick the user into executing SQL against a table name who's column names would contain the malicious SQL and subsequently invoke the `refreshRow()` method on the ResultSet. Note that the application's JDBC user and the schema owner need not be the same. A JDBC application that executes as a privileged user querying database schemas owned by potentially malicious less-privileged users would be vulnerable. In that situation it may be possible for the malicious user to craft a schema that causes the application to execute commands as the privileged user. Patched versions will be released as `42.2.26` and `42.4.1`. Users are advised to upgrade. There are no known workarounds for this issue.
What
PostgreSQL JDBC Driver (PgJDBC for short) allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. The PGJDBC implementation of the `java.sql.ResultRow.refreshRow()` method is not performing escaping of column names so a malicious column name that contains a statement terminator, e.g. `;`, could lead to SQL injection. This could lead to executing additional SQL commands as the application's JDBC user. User applications that do not invoke the `ResultSet.refreshRow()` method are not impacted. User application that do invoke that method are impacted if the underlying database that they are querying via their JDBC application may be under the control of an attacker. The attack requires the attacker to trick the user into executing SQL against a table name who's column names would contain the malicious SQL and subsequently invoke the `refreshRow()` method on the ResultSet. Note that the application's JDBC user and the schema owner need not be the same. A JDBC application that executes as a privileged user querying database schemas owned by potentially malicious less-privileged users would be vulnerable. In that situation it may be possible for the malicious user to craft a schema that causes the application to execute commands as the privileged user. Patched versions will be released as `42.2.26` and `42.4.1`. Users are advised to upgrade. There are no known workarounds for this issue.
Why
Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
What
PostgreSQL JDBC Driver (PgJDBC for short) allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. The PGJDBC implementation of the `java.sql.ResultRow.refreshRow()` method is not performing escaping of column names so a malicious column name that contains a statement terminator, e.g. `;`, could lead to SQL injection. This could lead to executing additional SQL commands as the application's JDBC user. User applications that do not invoke the `ResultSet.refreshRow()` method are not impacted. User application that do invoke that method are impacted if the underlying database that they are querying via their JDBC application may be under the control of an attacker. The attack requires the attacker to trick the user into executing SQL against a table name who's column names would contain the malicious SQL and subsequently invoke the `refreshRow()` method on the ResultSet. Note that the application's JDBC user and the schema owner need not be the same. A JDBC application that executes as a privileged user querying database schemas owned by potentially malicious less-privileged users would be vulnerable. In that situation it may be possible for the malicious user to craft a schema that causes the application to execute commands as the privileged user. Patched versions will be released as `42.2.26` and `42.4.1`. Users are advised to upgrade. There are no known workarounds for this issue.
Why
Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
- Likely attack path
- a network path → Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- Required interaction required
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-89 ↗
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'). The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- quarkus-jdbc-postgresql-deployment as a component of Red Hat build of Apicurio Registry 2
- jdbc-postgresql as a component of Red Hat Decision Manager 7
- autocorr-af (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-bg (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-ca (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-cs (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-da (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-de (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-en (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-es (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-fa (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-fi (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-fr (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-ga (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-hr (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-hu (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-is (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-it (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-ja (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-ko (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-lb (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-lt (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-mn (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-nl (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-pl (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-pt (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-ro (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-ru (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-sk (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- autocorr-sl (libreoffice:flatpak) as a component of Red Hat Enterprise Linux 8
- and 150 more
- Fixed
- Action
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 If the postgresql service is running, it will be automatically restarted after installing this update.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 3 Aug 2022 · Last source change 3 Nov 2025, 21:46 UTC · CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2022-6614
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- >= 42.2.0, < 42.2.26; >= 42.3.0, < 42.4.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- >= 42.2.0, < 42.2.26; >= 42.3.0, < 42.4.1 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 If the postgresql service is running, it will be automatically restarted after installing this update.
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.