Security readout for executives and security teams
Plain-English summary
CVE-2016-10610 affects the unicode-json Node.js module before 2.0.0. Those versions downloaded data over unencrypted HTTP, so someone positioned on the network could potentially alter what the package retrieved. The public sources do not provide CVSS scoring or evidence of active exploitation.
Executive priority
Handle as dependency hygiene with targeted urgency. It is not supported by the provided sources as actively exploited, but it can affect software supply-chain integrity where old Node dependencies are still used.
Technical view
The issue is classified as CWE-311: missing encryption of sensitive data. Affected unicode-json versions before 2.0.0 used HTTP for data resource downloads, creating a man-in-the-middle integrity risk during dependency use or installation workflows that retrieve those resources.
Likely exposure
Exposure is likely limited to projects that directly or transitively use unicode-json versions below 2.0.0, especially where installs or resource downloads occur over untrusted networks.
Exploitation context
The provided sources do not state active exploitation, and the CVE is not listed as KEV in the bundle. Practical risk depends on whether affected versions still fetch data over HTTP in the organization’s build, install, or runtime paths.
Researcher notes
Evidence is sparse: affected product, version range, CWE, and HTTP download behavior are identified, but no CVSS vector, exploit details, or operational impact specifics are provided in the bundle. Validate exposure through dependency inventory rather than assuming deployment impact.
Mitigation direction
- Upgrade unicode-json to version 2.0.0 or later.
- Check package-lock, yarn.lock, pnpm-lock, or SBOMs for unicode-json below 2.0.0.
- If upgrade is blocked, review vendor advisory guidance before applying compensating controls.
- Prefer trusted networks and controlled build environments for legacy dependency installation.
Validation and detection
- Search dependency manifests and lockfiles for unicode-json versions below 2.0.0.
- Confirm whether unicode-json is direct or transitive in affected applications.
- Review build logs for legacy resource downloads over HTTP.
- Re-scan dependency inventory after upgrading or removing affected versions.
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-10610 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/206CVE 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.