Security readout for executives and security teams
Plain-English summary
node-air-sdk fetched binary resources over plain HTTP. A person positioned on the network path could replace the downloaded binary, potentially leading to remote code execution. The sources list all versions as affected, but do not provide CVSS, confirmed exploitation, or a fixed version.
Executive priority
Treat this as a dependency hygiene and build-chain risk, not a confirmed active incident. Prioritize discovery in repositories and CI because binary substitution during setup could compromise developer or build environments.
Technical view
CVE-2016-10647 is a CWE-311 cleartext transport issue in the node-air-sdk Node module. Binary resources are downloaded over HTTP, creating a man-in-the-middle substitution risk. Impact may reach RCE if a swapped binary is executed. Exploitation requires network-path positioning or control of an intermediary.
Likely exposure
Exposure is likely limited to environments that install or use the node-air-sdk package and allow its binary download path. Build systems, developer workstations, and CI runners are the most relevant places to check.
Exploitation context
The bundle does not show KEV listing or active exploitation evidence. The attack depends on an attacker being on-path between the user and download server, or otherwise able to tamper with the HTTP binary transfer.
Researcher notes
The public record is sparse: all versions are listed affected, severity is unknown, and no CVSS or patch details are included. The key technical condition is HTTP binary retrieval, with potential RCE only if the substituted binary is executed.
Mitigation direction
- Inventory projects and lockfiles for node-air-sdk usage.
- Remove or replace node-air-sdk where feasible.
- Check vendor or package maintainer guidance for any supported fix.
- Avoid installing affected packages over untrusted networks.
- Restrict build and CI network paths where dependency downloads occur.
Validation and detection
- Review dependency manifests and lockfiles for node-air-sdk.
- Confirm whether CI or developer builds fetch AIR binaries through node-air-sdk.
- Check whether any download path uses plain HTTP for binary resources.
- Document affected repositories, build jobs, and runtime environments.
- Verify no source confirms active exploitation before escalating as exploited.
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-10647 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/250CVE 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.