Security readout for executives and security teams
Plain-English summary
CVE-2021-33460 is a crash flaw in Yasm 1.3.0. A specially formed input could trigger a NULL pointer dereference while Yasm processes NASM-style preprocessing conditions. The business impact is most likely build or processing disruption, not system takeover, based on the provided sources.
Executive priority
Treat this as a targeted operational risk for environments using Yasm 1.3.0. Prioritize inventory and upgrade validation where build systems process outside code, but avoid emergency response claims without stronger exploitation or severity evidence.
Technical view
The issue is a NULL pointer dereference in if_condition() in modules/preprocs/nasm/nasm-pp.c in Yasm 1.3.0. The source bundle provides no CVSS score, CWE, named patch, or affected CPE data beyond the product/version statement.
Likely exposure
Exposure is most relevant where Yasm 1.3.0 processes untrusted or externally supplied assembly/source inputs, such as build pipelines, developer tooling, packaging systems, or automated code analysis workflows.
Exploitation context
The CVE is not listed as KEV in the source bundle. The provided references show public disclosure artifacts, but the bundle does not establish active exploitation, weaponization, or a confirmed fixed version.
Researcher notes
Evidence is sparse: the bundle identifies the vulnerable function and version, but not impact beyond NULL pointer dereference, exploitability conditions, CVSS, CWE, or remediation. Analysis should stay constrained to crash/availability risk unless additional primary sources confirm more.
Mitigation direction
- Inventory systems and build images for Yasm 1.3.0.
- Check upstream Yasm guidance for a fixed release or patch status.
- Avoid processing untrusted assembly inputs with affected Yasm versions.
- Run build and parsing jobs with least privilege and isolation.
- Monitor CI or processing systems for repeatable Yasm crashes.
Validation and detection
- Confirm whether Yasm 1.3.0 is installed in developer and CI environments.
- Review workflows that pass external or user-supplied source files to Yasm.
- Check package manifests, SBOMs, containers, and build scripts for Yasm usage.
- Verify whether upstream guidance identifies an upgrade or patch.
- Correlate unexplained build failures with Yasm preprocessing activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2021-33460 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/yasm/yasm/issues/168CVE reference · x_refsource_MISC
- https://gist.github.com/Clingto/bb632c0c463f4b2c97e4f65f751c5e6dCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.