Skip to main content
VulnerabilityPublished Updated

CVE-2019-25013: GNU C Library · Out-of-bounds Read

Source CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jan 2021

  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

Affected software

ProductAffectedFixed in
Debiandebian/libc6pkg:deb/debian/libc6Other threatsAffected
  • <=2.32
Fixed in–
Ubuntuubuntu/libc6pkg:deb/ubuntu/libc6Other threatsAffected
  • <=2.32
Fixed in–
Red Hatredhat/glibcpkg:rpm/redhat/glibcOther threatsAffected
  • <=2.32
Fixed in–

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

AI-suggested

To mitigate CVE-2019-25013, European organizations should: 1) Ensure that all systems using glibc are updated to version 2.33 or later, where the vulnerability is patched. 2) Implement input validation and sanitization for all incoming data streams that may contain EUC-KR encoded text, rejecting malformed or suspicious multi-byte sequences before processing. 3) Employ application-level protections such as rate limiting and anomaly detection to identify and block attempts to supply malformed EUC-KR data that could trigger the vulnerability. 4) For critical services, consider isolating or sandboxing processes that perform character encoding conversions to limit the impact of potential crashes. 5) Monitor system logs and application behavior for signs of crashes or abnormal terminations related to iconv usage. 6) Where possible, disable or avoid the use of EUC-KR encoding conversions if not strictly necessary, or replace with more robust encoding schemes. These steps go beyond generic patching advice by emphasizing proactive input handling and operational monitoring tailored to the nature of this vulnerability.

Description

The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byte input sequences in the EUC-KR encoding, may have a buffer over-read.

References

Community reviews

Loading reviews…