Security readout for executives and security teams
Plain-English summary
CVE-2016-10635 affects old broccoli-closure npm package versions that fetched binary resources over unencrypted HTTP. A network-positioned attacker could replace the downloaded binary, creating possible remote code execution during development or build workflows.
Executive priority
Treat this as a legacy dependency cleanup issue with elevated concern where builds run on shared or untrusted networks. Prioritize internet-facing CI and release pipelines first.
Technical view
broccoli-closure before 1.3.1 used HTTP for binary resource downloads. This is a CWE-311 transport protection issue: integrity and confidentiality of the binary retrieval were not protected, enabling man-in-the-middle tampering under the right network conditions.
Likely exposure
Exposure is most likely in legacy JavaScript projects, CI images, or developer environments that still install or use broccoli-closure versions earlier than 1.3.1.
Exploitation context
The source bundle does not show known active exploitation or KEV listing. Exploitation requires an attacker positioned on the network path when the vulnerable package downloads its binary resource.
Researcher notes
The public data gives a clear affected version boundary and attack condition, but no CVSS, confirmed exploit reports, or detailed vendor remediation notes beyond versions before 1.3.1 being affected.
Mitigation direction
- Inventory package manifests and lockfiles for broccoli-closure.
- Upgrade broccoli-closure to 1.3.1 or later where present.
- Rebuild CI and developer images using updated dependency locks.
- If upgrade is not feasible, check vendor guidance for supported alternatives.
- Avoid running legacy dependency installs on untrusted networks.
Validation and detection
- Search package-lock, yarn.lock, pnpm-lock, and package manifests for broccoli-closure.
- Confirm resolved versions are not earlier than 1.3.1.
- Review CI build logs for legacy broccoli-closure installation paths.
- Check container and build images for cached vulnerable dependency trees.
- Document any remaining exception and compensating controls.
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-10635 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/242CVE 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.