Skip to main content
CVE-2023-39417VulnerabilityPublished Updated

CVE-2023-39417: Red Hat Advanced Cluster Security 4.2 · SQL Injection

Affects Red Hat Advanced Cluster Security 4.2Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

1. Immediately review and apply any available patches or updates from Red Hat for Advanced Cluster Security and PostgreSQL extensions to address this vulnerability. 2. Audit and restrict database-level privileges, specifically the CREATE privilege, to the minimum necessary users and roles to reduce the attack surface. 3. Conduct a thorough inventory of installed PostgreSQL extensions, focusing on non-bundled and trusted extensions, and assess their necessity and security posture. 4. Implement strict input validation and sanitization practices for any database operations involving extension scripts or dynamic SQL generation. 5. Employ database activity monitoring and anomaly detection to identify unusual CREATE operations or privilege escalations. 6. Use role-based access control (RBAC) and principle of least privilege (PoLP) to limit administrative access to database components. 7. Regularly back up critical databases and verify recovery procedures to mitigate impact in case of compromise. 8. Engage in security awareness training for database administrators regarding secure extension management and privilege assignment. 9. Consider network segmentation and isolation of database servers to limit exposure to potential attackers. 10. Monitor security advisories from Red Hat and PostgreSQL communities for updates or emerging exploit information.

Description

IN THE EXTENSION SCRIPT, a SQL Injection vulnerability was found in PostgreSQL if it uses @extowner@, @extschema@, or @extschema:...@ inside a quoting construct (dollar quoting, '', or ""). If an administrator has installed files of a vulnerable, trusted, non-bundled extension, an attacker with database-level CREATE privilege can execute arbitrary code as the bootstrap superuser.

References

Community reviews

Loading reviews…