CVE-2022-31197 is an SQL injection vulnerability in the PostgreSQL JDBC Driver (PgJDBC) implementation of java.sql.ResultSet.refreshRow(). The driver constructs SQL using result-set column names without correctly escaping those identifiers. A malicious column name containing a statement terminator can therefore inject additional SQL statements when an application invokes refreshRow() on the affected ResultSet. Injected statements execute with the privileges of the JDBC connection user.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A SQL-injection vulnerability in PostgreSQL JDBC's ResultSet.refreshRow() caused by malicious column names.
A SQL-injection vulnerability in PostgreSQL's ResultSet.refreshRow() involving malicious column names.
Vulnerability observed in exploitation telemetry (details not specified in the content).
Unknown (content lists this CVE in activity tables without describing the vulnerability).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.