LiveActive security incident?Get immediate response
CVE Record

CVE-2020-35342: GNU Binutils before 2.34 has an uninitialized-heap vulnerability in function tic4x_print_cond (file opcodes...

GNU Binutils before 2.34 has an uninitialized-heap vulnerability in function tic4x_print_cond (file opcodes/tic4x-dis.c) which could allow attackers to make an information leak.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-35342 is an information-leak issue in GNU Binutils before 2.34. It involves uninitialized heap data in a disassembly function. Business urgency is usually limited unless affected tools process untrusted binaries, firmware, or uploaded files in automated workflows.

Executive priority

Treat this as a targeted exposure-management item, not an emergency based on current evidence. Prioritize internet-facing upload pipelines, malware-analysis environments, and shared CI systems that process untrusted binary content.

Technical view

The reported flaw is in tic4x_print_cond in opcodes/tic4x-dis.c. GNU Binutils versions before 2.34 may expose uninitialized heap memory while handling crafted input. The source bundle does not provide CVSS, CWE, detailed exploitability, or affected downstream package lists.

Likely exposure

Exposure is most likely in build, reverse-engineering, malware-analysis, firmware-analysis, or CI systems running GNU Binutils before 2.34 against untrusted files. Downstream products may embed affected components, but the bundle only cites NetApp guidance without specific affected versions here.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The plausible risk is targeted information disclosure when an attacker can cause affected Binutils tooling to parse a malicious binary-like file.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed affected product matrix is provided. Analysis should focus on Binutils provenance, version validation, backported patches, and whether the tic4x disassembly path is reachable in local workflows.

Mitigation direction

  • Upgrade GNU Binutils to 2.34 or later where applicable.
  • Use operating-system and appliance vendor advisories for packaged Binutils updates.
  • Limit affected tooling from processing untrusted files until patched.
  • Run binary-analysis workflows in isolated, least-privileged environments.
  • Check NetApp guidance if using NetApp products or managed appliances.

Validation and detection

  • Inventory GNU Binutils versions across hosts, containers, CI images, and analysis systems.
  • Identify workflows that process externally supplied binaries, firmware, or object files.
  • Confirm whether distro packages backport the fix despite older version strings.
  • Review vendor advisories for embedded or appliance-specific exposure.
  • Document any compensating isolation controls for unpatched systems.
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-2020-35342 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.