Skip to main content
VulnerabilityPublished Updated

CVE-2023-5869: Red Hat Advanced Cluster Security 4.2 · Integer Overflow or Wraparound

Affects Red Hat Advanced Cluster Security 4.2Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Dec 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 26 Oct 2026.

What to do

AI-suggested

European organizations should immediately audit their use of Red Hat Advanced Cluster Security 4.2 and associated PostgreSQL instances to identify vulnerable deployments. Until patches are released, restrict database access to trusted users and networks, employing strict authentication and authorization controls. Implement network segmentation to isolate database servers from less secure network zones. Monitor database logs and system behavior for unusual activity indicative of exploitation attempts, such as abnormal memory usage or unexpected SQL array modifications. Employ application-layer firewalls or database activity monitoring tools to detect and block suspicious queries. Regularly update and patch Red Hat and PostgreSQL software as soon as security updates become available. Conduct thorough credential management, including rotating passwords and enforcing multi-factor authentication for database users. Additionally, consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect anomalous code execution patterns. Finally, prepare incident response plans tailored to database compromise scenarios to minimize damage if exploitation occurs.

Description

A flaw was found in PostgreSQL that allows authenticated database users to execute arbitrary code through missing overflow checks during SQL array value modification. This issue exists due to an integer overflow during array modification where a remote user can trigger the overflow by providing specially crafted data. This enables the execution of arbitrary code on the target system, allowing users to write arbitrary bytes to memory and extensively read the server's memory.

References

Community reviews

Loading reviews…