Skip to main content
VulnerabilityPublished Updated

CVE-2023-52389: Integer Overflow or Wraparound

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.13.0 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jan 2024

  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

Upgrade pocoproject/poco to 1.13.0.

Affected software

ProductAffectedFixed in
GitHubpocoproject/pocopkg:github/pocoproject/pocoOther threatsAffected
  • <1.13.0
Fixed in
  • 1.13.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately inventory their software assets to identify any use of POCO C++ Libraries, particularly versions prior to 1.11.8p2, 1.12.5p2, or 1.13.0. They should prioritize upgrading to these patched versions to eliminate the vulnerability. For software vendors or developers unable to upgrade immediately, applying source-level patches or recompiling with custom fixes may be necessary. Implementing runtime protections such as stack canaries, Address Space Layout Randomization (ASLR), and Data Execution Prevention (DEP) can help mitigate exploitation impact. Network-level controls, including intrusion detection systems (IDS) and web application firewalls (WAF), should be tuned to detect anomalous UTF-32 encoded payloads or suspicious traffic patterns. Additionally, organizations should monitor security advisories for any emerging exploit code and prepare incident response plans to quickly address potential compromises.

Description

UTF32Encoding.cpp in POCO has a Poco::UTF32Encoding integer overflow and resultant stack buffer overflow because Poco::UTF32Encoding::convert() and Poco::UTF32::queryConvert() may return a negative integer if a UTF-32 byte sequence evaluates to a value of 0x80000000 or higher. This is fixed in 1.11.8p2, 1.12.5p2, and 1.13.0.

References

Community reviews

Loading reviews…