Security readout for executives and security teams
Plain-English summary
Older limbus-buildgen versions fetched binary resources over unencrypted HTTP. Someone able to intercept that network traffic could replace those downloads with malicious binaries, potentially causing code execution in the build environment. The sources do not report active exploitation, and no CVSS score is provided.
Executive priority
Treat as a targeted build-chain risk, not a broad emergency. Prioritize remediation if the dependency appears in active CI, release packaging, or developer bootstrap workflows.
Technical view
CVE-2016-10674 affects the limbus-buildgen Node module before 0.1.1. It is mapped to CWE-311 because binary resources were downloaded over HTTP. A network-positioned attacker could tamper with those resources, creating possible RCE during builds. Public sources do not provide exploit details or broader product impact.
Likely exposure
Exposure is likely limited to projects or build pipelines that still use limbus-buildgen versions below 0.1.1. Risk is higher on untrusted or interceptable networks and where build outputs execute downloaded binaries.
Exploitation context
No KEV listing or cited source indicates active exploitation. The described attack requires network positioning between the user and remote server. The source bundle states possible RCE but does not prove weaponized exploitation.
Researcher notes
Evidence is sparse: the bundle identifies the affected npm module, version boundary, CWE, and MITM-to-possible-RCE condition. No CVSS, exploit status, or detailed patch notes are included.
Mitigation direction
- Upgrade limbus-buildgen to version 0.1.1 or later where present.
- Review vendor or advisory guidance before accepting build-system exceptions.
- Remove unused limbus-buildgen dependencies from projects and CI images.
- Avoid build workflows that fetch executable resources over plain HTTP.
Validation and detection
- Check dependency manifests and lockfiles for limbus-buildgen below 0.1.1.
- Review CI images and cached build environments for the vulnerable module.
- Confirm build pipelines do not depend on HTTP-fetched binary resources.
- Document any remaining use and associated network trust assumptions.
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.
CWE-311: 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 lookupExecution 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 lookupCVE-2016-10674 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://nodesecurity.io/advisories/276CVE 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.
Missing Encryption of Sensitive Data
Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.