CVE-2024-1597

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2024-02-21. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2024-0465 (ENISA EUVD) · GHSA-24rp-q3w6-vc56 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 4.8%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
4.8%
EPSS %ILE
92nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
4.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 19, 2024

Last Modified

November 3, 2025

Advisory Details (7)

Auto-updated Nov 8, 2026
Patch available. Sources: github.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3812-1] libpgjava security update

https://lists.debian.org/debian-lts-announce/2024/05/msg00007.html
GitHub advisoryMentions a patch (unverified)

SQL Injection via line comment generation · Advisory · pgjdbc/pgjdbc · GitHub

https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-24rp-q3w6-vc56
Web page

oss-security - CVE-2024-1597: PostgreSQL pgjdbc: SQL injection in non-default configuration

http://www.openwall.com/lists/oss-security/2024/04/02/6
Web page

EDB Docs - CVE-2024-1597 - SQL Injection via line comment generation

https://www.enterprisedb.com/docs/security/assessments/cve-2024-1597/
Web page

EDB Docs - JDBC Connector v42.7.3.5 - Release notes

https://www.enterprisedb.com/docs/jdbc_connector/latest/01_jdbc_rel_notes/
Web page

[SECURITY] Fedora 40 Update: postgresql-jdbc-42.7.3-1.fc40 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/TZQTSMESZD2RJ5XBPSXH3TIQVUW5DIUU/

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpgjdbc2024-08-06redhat
redhatpostgresql-jdbc-0:42.2.3-5.el8_62024-07-09redhat
redhatpostgresql-jdbc-0:42.2.3-7.el8_42024-07-08redhat
redhatopenshift-serverless-1/logic-swf-devmode-rhel8:1.33.0-52024-06-24redhat
redhatpostgresql-jdbc-0:42.2.14-5.el8_82024-05-23redhat
redhatpostgresql-jdbc-0:42.2.3-5.el8_22024-04-30redhat
redhatpostgresql-jdbc-0:42.2.28-1.el9_02024-04-23redhat
redhatorg.postgresql/postgresql:42.5.6.redhat-000012024-04-22redhat
redhatrh-sso-7/sso7-rhel8-operator-bundle:7.6.7-42024-04-04redhat
redhatorg.postgresql/postgresql:42.6.1.redhat-000012024-04-03redhat
redhatpostgresql-jdbc-0:42.2.28-1.el9_22024-04-02redhat
redhatpostgresql-jdbc-0:42.2.28-1.el9_32024-03-20redhat
redhatpostgresql-jdbc-0:42.2.14-3.el8_92024-03-20redhat
mavenorg.postgresql:postgresql @ 42.2.28 (fixes < 42.2.28)—ghsa
mavenorg.postgresql:postgresql @ 42.3.9 (fixes >= 42.3.0, < 42.3.9)—ghsa
mavenorg.postgresql:postgresql @ 42.6.1 (fixes >= 42.6.0, < 42.6.1)—ghsa
mavenorg.postgresql:postgresql @ 42.7.2 (fixes >= 42.7.0, < 42.7.2)—ghsa
mavenorg.postgresql:postgresql @ 42.4.4 (fixes >= 42.4.0, < 42.4.4)—ghsa
mavenorg.postgresql:postgresql @ 42.5.5 (fixes >= 42.5.0, < 42.5.5)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 12 ecosystems)
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
java-postgresql-jdbc—
  • every version up to 42.6.2-r0: fixed in 42.6.2-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
java-postgresql-jdbc—
  • every version up to 42.6.2-r0: fixed in 42.6.2-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
java-postgresql-jdbc—
  • every version up to 42.6.2-r0: fixed in 42.6.2-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
java-postgresql-jdbc—
  • every version up to 42.6.2-r0: fixed in 42.6.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
java-postgresql-jdbc—
  • every version up to 42.6.2-r0: fixed in 42.6.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
java-postgresql-jdbc—
  • every version up to 42.6.2-r0: fixed in 42.6.2-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.2.5-2, 42.2.5-2+deb10u1, 42.2.5-2+deb10u2, 42.2.5-2+deb10u3
  • every version up to 42.2.5-2+deb10u4: fixed in 42.2.5-2+deb10u4
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.2.15-1, 42.2.15-1+deb11u1
  • every version up to 42.2.15-1+deb11u2: fixed in 42.2.15-1+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.5.4-1
  • every version up to 42.5.5-0+deb12u1: fixed in 42.5.5-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava—
  • every version up to 42.7.2-1: fixed in 42.7.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava—
  • every version up to 42.7.2-1: fixed in 42.7.2-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.postgresql:postgresql42.7.0, 42.7.1
  • every version up to 42.2.28: fixed in 42.2.28
  • 42.3.0 up to 42.3.9: fixed in 42.3.9
  • 42.4.0 up to 42.4.4: fixed in 42.4.4
  • 42.5.0 up to 42.5.5: fixed in 42.5.5
  • 42.6.0 up to 42.6.1: fixed in 42.6.1
  • 42.7.0 up to 42.7.2: fixed in 42.7.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 23× in last 7d / 77× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 301 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 201 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 07:15 UTCEchelonGraph re-scored
  2. 2026-11-13 07:15 UTCVendor advisory
  3. 2026-11-13 07:15 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  4. 2026-11-12 16:30 UTCEPSS rescoreEPSS 4.8% · 92nd percentile
  5. 2026-11-12 09:30 UTCEchelonGraph re-scored
  6. 2026-11-12 09:30 UTCVendor advisory
  7. 2026-11-12 09:30 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  8. 2026-11-11 16:34 UTCEPSS rescoreEPSS 4.8% · 92nd percentile
  9. 2026-11-11 11:52 UTCEchelonGraph re-scored
  10. 2026-11-11 11:52 UTCVendor advisory
  11. 2026-11-11 11:52 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  12. 2026-11-10 16:38 UTCEPSS rescoreEPSS 4.8% · 92nd percentile
  13. 2026-11-10 14:13 UTCVendor advisory
  14. 2026-11-10 14:13 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  15. 2026-11-09 16:34 UTCEchelonGraph re-scored
  16. 2026-11-09 16:34 UTCVendor advisory
  17. 2026-11-09 16:34 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  18. 2026-11-09 16:30 UTCEPSS rescoreEPSS 4.8% · 92nd percentile
  19. 2026-11-08 18:56 UTCEchelonGraph re-scored
  20. 2026-11-08 18:56 UTCVendor advisory
  21. 2026-11-08 18:56 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  22. 2026-11-08 16:35 UTCEPSS rescoreEPSS 4.8% · 92nd percentile
  23. 2026-11-07 21:17 UTCEchelonGraph re-scored
  24. 2026-11-07 21:17 UTCVendor advisory
  25. 2026-11-07 21:17 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
Show 75 more
  1. 2026-11-07 16:35 UTCEPSS rescoreEPSS 4.8% · 92nd percentile
  2. 2026-11-06 23:38 UTCEchelonGraph re-scored
  3. 2026-11-06 23:38 UTCVendor advisory
  4. 2026-11-06 23:38 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  5. 2026-11-06 16:31 UTCEPSS rescoreEPSS 4.8% · 92nd percentile
  6. 2026-11-06 02:00 UTCEchelonGraph re-scored
  7. 2026-11-06 02:00 UTCVendor advisory
  8. 2026-11-06 02:00 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  9. 2026-11-05 16:33 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  10. 2026-11-05 04:22 UTCEchelonGraph re-scored
  11. 2026-11-05 04:22 UTCVendor advisory
  12. 2026-11-05 04:22 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  13. 2026-11-04 21:25 UTCOSV refresh
  14. 2026-11-04 16:32 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  15. 2026-11-04 06:40 UTCEchelonGraph re-scored
  16. 2026-11-04 06:40 UTCVendor advisory
  17. 2026-11-04 06:40 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  18. 2026-11-03 16:41 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  19. 2026-11-03 09:01 UTCEchelonGraph re-scored
  20. 2026-11-03 09:01 UTCVendor advisory
  21. 2026-11-03 09:01 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  22. 2026-11-02 11:23 UTCEchelonGraph re-scored
  23. 2026-11-02 11:23 UTCVendor advisory
  24. 2026-11-02 11:23 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  25. 2026-11-01 13:43 UTCVendor advisory
  26. 2026-11-01 13:43 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  27. 2026-11-01 08:16 UTCGHSA enrichmentGHSA-24rp-q3w6-vc56 · GitHub severity CRITICAL · GitHub CVSS 10.0
  28. 2026-11-01 08:16 UTCEchelonGraph re-scored
  29. 2026-10-31 16:30 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  30. 2026-10-31 16:04 UTCVendor advisory
  31. 2026-10-30 18:23 UTCEchelonGraph re-scored
  32. 2026-10-30 18:23 UTCVendor advisory
  33. 2026-10-30 16:31 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  34. 2026-10-29 20:45 UTCEchelonGraph re-scored
  35. 2026-10-29 20:45 UTCVendor advisory
  36. 2026-10-29 16:30 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  37. 2026-10-28 23:06 UTCEchelonGraph re-scored
  38. 2026-10-28 23:06 UTCVendor advisory
  39. 2026-10-28 16:29 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  40. 2026-10-28 01:28 UTCEchelonGraph re-scored
  41. 2026-10-28 01:28 UTCVendor advisory
  42. 2026-10-27 16:29 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  43. 2026-10-27 03:43 UTCEchelonGraph re-scored
  44. 2026-10-27 03:43 UTCVendor advisory
  45. 2026-10-26 16:29 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  46. 2026-10-26 01:52 UTCVendor advisory
  47. 2026-10-25 17:20 UTCEchelonGraph re-scored
  48. 2026-10-25 16:30 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  49. 2026-10-25 04:13 UTCEchelonGraph re-scored
  50. 2026-10-25 04:13 UTCVendor advisory
  51. 2026-10-24 16:30 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  52. 2026-10-24 06:33 UTCEchelonGraph re-scored
  53. 2026-10-24 06:33 UTCVendor advisory
  54. 2026-10-23 16:29 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  55. 2026-10-23 08:52 UTCEchelonGraph re-scored
  56. 2026-10-23 08:52 UTCVendor advisory
  57. 2026-10-22 16:31 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  58. 2026-10-22 11:08 UTCEchelonGraph re-scored
  59. 2026-10-22 11:08 UTCVendor advisory
  60. 2026-10-21 16:29 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  61. 2026-10-21 13:29 UTCEchelonGraph re-scored
  62. 2026-10-21 13:29 UTCVendor advisory
  63. 2026-10-20 16:30 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  64. 2026-10-20 15:13 UTCEchelonGraph re-scored
  65. 2026-10-20 15:13 UTCVendor advisory
  66. 2026-10-19 16:29 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  67. 2026-10-19 15:28 UTCVendor advisory
  68. 2026-10-18 17:48 UTCEchelonGraph re-scored
  69. 2026-10-18 17:48 UTCVendor advisory
  70. 2026-10-18 16:29 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  71. 2026-10-18 07:30 UTCEchelonGraph re-scored
  72. 2026-10-17 20:08 UTCEchelonGraph re-scored
  73. 2026-10-17 20:08 UTCVendor advisory
  74. 2026-10-17 16:30 UTCEPSS rescoreEPSS 4.8% · 91st percentile
  75. 2026-10-16 22:26 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2024-1597?
CVE-2024-1597 is a critical-severity vulnerability; its CVE record was published on February 19, 2024. 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…
When was the CVE record for CVE-2024-1597 published?
The CVE record for CVE-2024-1597 was published on February 19, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2024-1597 actively exploited?
CVE-2024-1597 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.8% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-1597?
CVE-2024-1597 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2024-1597?
A fix for CVE-2024-1597 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-1597 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-1597

Explore →

Is Your Infrastructure Affected by CVE-2024-1597?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.