LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32256: An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.36.

An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.36. It is a stack-overflow issue in demangle_type in rust-demangle.c.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-32256 is a stack overflow in GNU libiberty, shipped with GNU Binutils 2.36. It affects code that demangles Rust symbols. Business risk depends on whether vulnerable tooling processes untrusted binaries or symbol data. The provided sources do not include CVSS, CWE, affected CPEs, or a named fix.

Executive priority

Treat as an inventory and vendor-remediation item, not an emergency based on the provided evidence. Escalate priority if vulnerable tooling processes untrusted binaries at scale or if a vendor advisory confirms affected production appliances.

Technical view

The issue is in demangle_type in rust-demangle.c within GNU libiberty as distributed in GNU Binutils 2.36. The source bundle identifies a stack-overflow condition but does not describe trigger details, exploitability, patch commit, or downstream version ranges beyond Binutils 2.36.

Likely exposure

Most likely exposure is developer, build, debugging, analysis, or appliance environments using Binutils/libiberty 2.36 to process Rust symbol names. The source bundle lists affected vendor and product as n/a, so exact product exposure must be confirmed through local package and vendor inventory.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation. A stack overflow in a demangler is most concerning when untrusted binaries, object files, crash artifacts, or symbol strings are processed automatically by vulnerable tooling.

Researcher notes

Evidence is sparse. The CVE description names the vulnerable function and Binutils 2.36, while references point to Launchpad and NetApp. No CVSS, CWE, exploit status, patch identifier, or complete affected-version matrix is provided in the bundle.

Mitigation direction

  • Inventory GNU Binutils and libiberty versions across servers, build systems, appliances, and analysis tools.
  • Check GNU, OS distribution, Ubuntu, and NetApp guidance for fixed packages or supported workarounds.
  • Prioritize replacing Binutils 2.36 where a vendor-supported fixed package is available.
  • Limit automated processing of untrusted binaries or symbol data until exposure is resolved.
  • Track vendor advisories because the source bundle does not name a specific patch.

Validation and detection

  • Confirm whether any systems run GNU Binutils or libiberty version 2.36.
  • Identify workflows that demangle Rust symbols from untrusted or external files.
  • Review vendor package metadata for security fixes addressing CVE-2021-32256.
  • Check crash logs for demangling-related stack overflow failures in relevant tooling.
  • Document false positives where libiberty is present but not reachable by untrusted input.
Prepared
Confidence
medium
Sources
4

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.

cve · low confidence lookup

CVE-2021-32256 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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