LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25013: The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byt...

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.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-25013 is a glibc iconv flaw that can read past a buffer while handling malformed EUC-KR text. The main business risk is service disruption, not data theft or system takeover, based on the CVSS vector. Prioritize systems and containers using older glibc/libc6 builds, especially where untrusted text conversion is exposed.

Executive priority

Handle in normal vulnerability management cadence, with faster action for internet-facing services or critical systems that process untrusted text. This is not evidenced as actively exploited, but availability impact and broad glibc distribution justify remediation tracking.

Technical view

The issue is CWE-125 in GNU C Library iconv through 2.32. Invalid multibyte EUC-KR input may trigger a buffer over-read. CVSS 3.1 is 5.9: network reachable, high attack complexity, no privileges or user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact.

Likely exposure

Exposure is likely on Linux hosts, appliances, and container images carrying affected glibc/libc6 packages. The bundle lists generic affected data as unavailable, so confirm through OS package metadata and vendor advisories rather than product assumptions.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation is rated high complexity and appears tied to malformed EUC-KR conversion paths. Treat scanner findings seriously, but validate whether the affected glibc package is actually present and reachable.

Researcher notes

The strongest evidence is the CVE record, Sourceware bug, upstream commit reference, and multiple vendor advisories. Affected product metadata in the bundle is incomplete, so researchers should avoid broad product claims and focus on package-level validation.

Mitigation direction

  • Apply vendor glibc/libc6 security updates for affected operating systems and images.
  • Check upstream glibc commit and distribution advisories for fixed package lineage.
  • Rebuild containers and base images that include vulnerable glibc packages.
  • Reduce exposure of untrusted EUC-KR conversion paths where practical.
  • Track vendor guidance for appliances or bundled Linux runtimes.

Validation and detection

  • Inventory glibc/libc6 package versions across hosts, containers, and appliances.
  • Confirm whether versions are through glibc 2.32 or vendor-marked vulnerable builds.
  • Validate scanner findings against distribution security advisories and package changelogs.
  • Identify services that process untrusted text through iconv or EUC-KR conversion.
  • Retest after updates to confirm CVE findings clear.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-25013 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
18Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2019-25013Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.