Security readout for executives and security teams
Plain-English summary
This is a supply-chain integrity issue in an old Node module used to install go-ipfs dependencies. Versions before 0.4.4 fetched resources over HTTP during installation, so someone positioned on the network could tamper with what was installed.
Executive priority
Treat this as a targeted legacy dependency cleanup item, not an emergency internet-facing issue. Prioritize systems that still build old IPFS-related projects or run untrusted-network CI installs.
Technical view
go-ipfs-dep/go-ipfs-deps before 0.4.4 used insecure HTTP resource downloads during install. The CVE maps to CWE-311 and describes a man-in-the-middle risk that could compromise downloaded resources and potentially the environment using them.
Likely exposure
Exposure is most likely in legacy projects, CI jobs, or developer environments that installed go-ipfs-dep/go-ipfs-deps versions below 0.4.4. Current exposure depends on whether old dependency trees or lockfiles are still used.
Exploitation context
The provided sources do not show known active exploitation, and the CVE is not listed as KEV. Exploitation would require an attacker able to interfere with installation traffic over the network.
Researcher notes
Evidence is limited to the CVE description, affected version range, Node Security advisory reference, and GitHub pull request reference. No CVSS vector, exploit proof, or confirmed active exploitation is provided in the bundle.
Mitigation direction
- Upgrade go-ipfs-dep/go-ipfs-deps to 0.4.4 or later where still used.
- Remove the dependency if it is no longer required.
- Rebuild environments from trusted dependency sources after updating.
- Check vendor or project guidance for any additional remediation details.
Validation and detection
- Search manifests and lockfiles for go-ipfs-dep or go-ipfs-deps versions below 0.4.4.
- Review CI and build images for cached legacy package installations.
- Confirm new installs no longer fetch install resources over plain HTTP.
- Check historical build logs if compromise during past installs is a concern.
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 lookupCVE-2016-10563 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/156CVE reference · x_refsource_MISC
- https://github.com/diasdavid/go-ipfs-dep/pull/12CVE 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.