LiveActive security incident?Get immediate response
CVE Record

CVE-2017-10686: In Netwide Assembler (NASM) 2.14rc0, there are multiple heap use after free vulnerabilities in the tool nasm.

In Netwide Assembler (NASM) 2.14rc0, there are multiple heap use after free vulnerabilities in the tool nasm. The related heap is allocated in the token() function and freed in the detoken() function (called by pp_getline()) - it is used again at multiple positions later that could cause multiple damages. For example, it causes a corrupted double-linked list in detoken(), a double free or corruption in delete_Token(), and an out-of-bounds write in detoken(). It has a high possibility to lead to a remote code execution attack.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

NASM 2.14rc0 has memory safety flaws that can crash the assembler and may allow code execution when it processes malicious assembly input. This matters most where NASM runs automatically in build systems, CI, packaging pipelines, or developer workstations that handle untrusted source code.

Executive priority

Treat this as a high-priority build-chain issue, not a typical perimeter exposure. Patch systems that compile code first, because compromise there can affect produced software and downstream deployments.

Technical view

The CVE describes multiple heap use-after-free conditions in nasm. Memory allocated in token() is freed through detoken(), called by pp_getline(), then reused later. Reported outcomes include allocator list corruption, double free or corruption in delete_Token(), and an out-of-bounds write in detoken().

Likely exposure

Exposure is most likely on systems running NASM 2.14rc0 or vulnerable distribution packages, especially build hosts and CI images. Internet-facing exposure is unlikely unless a service accepts assembly input and invokes NASM server-side.

Exploitation context

The provided sources do not show known active exploitation, and this CVE is not marked KEV. The vulnerability requires NASM to process crafted input; the source description says it has high potential for remote code execution, but exploit availability is not established here.

Researcher notes

Evidence is strongest for NASM 2.14rc0 and distribution advisories. The source bundle does not include CVSS, CWE mapping, exact fixed versions, or confirmed exploitation. Avoid expanding affected scope beyond NASM and vendor-documented packages.

Mitigation direction

  • Inventory developer systems, build hosts, and CI images for NASM 2.14rc0.
  • Apply NASM security updates from Ubuntu, Gentoo, or the relevant package vendor.
  • Avoid processing untrusted assembly files with vulnerable NASM until patched.
  • Rebuild toolchain containers and build images from patched bases.
  • Check vendor advisories for fixed package versions in each supported environment.

Validation and detection

  • Confirm installed NASM versions on endpoints, build servers, and containers.
  • Compare package versions against Ubuntu, Gentoo, or local distribution advisories.
  • Review CI jobs for workflows that assemble third-party or user-supplied code.
  • Verify patched images are used by build pipelines after remediation.
Prepared
Confidence
medium
Sources
5

Public sources used

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-10686 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
4Source links

CVSS and timeline data

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

Source materials

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.