CVE-2023-52389

Pocoproject Poco vulnerability

9.8 CRITICALEPSS 0.85%

Published27 Jan 2024

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Pocoproject Poco≥ 1.12.0 < 1.12.5 · < 1.11.8 · 1.11.8 · 1.12.5

Remediation

Fixed in

Pocoproject Poco≥ 1.12.5

Frequently asked

Is CVE-2023-52389 being actively exploited?

CVE-2023-52389 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.85%.

How severe is CVE-2023-52389?

CVE-2023-52389 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.85% probability of exploitation.

Which products are affected by CVE-2023-52389?

Affected products include Pocoproject Poco.

How do I fix CVE-2023-52389?

Upgrade affected software to a fixed version, for example Pocoproject Poco 1.12.5 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2023-52389 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.