CVE-2024-1597:The PostgreSQL JDBC Driver, pgjdbc, has a SQL Injection vulnerability when using PreferQueryMode=SIMPLE. This allows an attacker to inject SQL and 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.

splash
Back

Description Preview

The pgjdbc, the PostgreSQL JDBC Driver, has a vulnerability that allows an attacker to inject SQL if using PreferQueryMode=SIMPLE. This is not the default mode and 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.

Overview

The vulnerability is identified as CVE-2024-1597 and was published on 2024-02-19. The vulnerability is critical with a CVSS base score of 10. The vulnerability is due to improper neutralization of special elements used in an SQL command, leading to SQL Injection. The vulnerability can be exploited over the network with low complexity and does not require user interaction or privileges.

Remediation

Users are advised not to use the SimpleQuery mode. They should update their pgjdbc to versions 42.7.2, 42.6.1, 42.5.5, 42.4.4, 42.3.9, or 42.2.28 and above to mitigate this vulnerability.

References

  1. GitHub Security Advisory
  2. EnterpriseDB Assessment
  3. EnterpriseDB JDBC Release Notes
  4. Fedora Project Package Announcement
  5. NetApp Security Advisory
  6. OpenWall OSS Security
  7. Debian LTS Announcement

Industry ExposureMost to least
This section illustrates the prevalence of a specific Common Vulnerabilities and Exposures (CVE) across various industries based on customer reports. The ranking displays industries from the most to least affected by this particular vulnerability, offering valuable insight into where this CVE has been most frequently observed. This information can help organizations within these sectors prioritize their security efforts, understand their relative risk exposure compared to their peers, and focus remediation strategies where they are most needed. By understanding the industry-specific impact, organizations can make more informed decisions regarding patching, resource allocation, and overall risk management related to this CVE.

  1. Manufacturing
    Manufacturing
  2. Public Administration
    Public Administration
  3. Professional, Scientific, & Technical Services
    Professional, Scientific, & Technical Services
  4. Health Care & Social Assistance
    Health Care & Social Assistance
  5. Educational Services
    Educational Services
  6. Retail Trade
    Retail Trade
  7. Transportation & Warehousing
    Transportation & Warehousing
  8. Arts, Entertainment & Recreation
    Arts, Entertainment & Recreation
  9. Finance and Insurance
    Finance and Insurance
  10. Management of Companies & Enterprises
    Management of Companies & Enterprises
  11. Other Services (except Public Administration)
    Other Services (except Public Administration)
  12. Utilities
    Utilities
  13. Wholesale Trade
    Wholesale Trade
  14. Accommodation & Food Services
    Accommodation & Food Services
  15. Administrative, Support, Waste Management & Remediation Services
    Administrative, Support, Waste Management & Remediation Services
  16. Agriculture, Forestry Fishing & Hunting
    Agriculture, Forestry Fishing & Hunting
  17. Construction
    Construction
  18. Information
    Information
  19. Mining
    Mining
  20. Real Estate Rental & Leasing
    Real Estate Rental & Leasing

Focus on What Matters

  1. See Everything.
  2. Identify True Risk.
  3. Proactively Mitigate Threats.

Let's talk!

background
Armis Vulnerability Intelligence Database