Vulnerabilities in pkg:npm/unicode-json

PACKAGE
Advisory Identifier: GHSA-hw4r-xr38-hm8j
Advisory Summary

CVE-2016-10610 is a HIGH remote code execution vulnerability (CWE-311: Missing Encryption of Sensitive Data) affecting Unicode json libraries in the npm ecosystem. The issue involves downloads resources over http in unicode-json. Remediation is available by upgrading affected packages to version 2.0.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/unicode-json

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/unicode-json. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-hw4r-xr38-hm8j CVE-2016-10610 HIGH Downloads Resources over HTTP in unicode-json

CVE-2016-10610 at a Glance

CVE Identifier CVE-2016-10610
GHSA Identifier GHSA-hw4r-xr38-hm8j
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-311: Missing Encryption of Sensitive Data
Affected Product Unicode json
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2016-10610

To remediate this vulnerability, upgrade all affected Unicode json dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

unicode-json fixed: 2.0.0
npm install unicode-json@2.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls unicode-json

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2016-10610, inspect your project dependencies using npm:

npm ls unicode-json

Analyze the terminal output to locate any version of Unicode json in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.0), your application is affected.

Note: The npm ls unicode-json command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-311: Missing Encryption of Sensitive Data, where the product does not encrypt sensitive or critical information before storage or transmission. In Unicode json, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Affected versions of `unicode-json` insecurely downloads resources over HTTP. In scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution. ## Recommendation Install version 2.0.0 or greater.

CVE-2016-10610 Affected Unicode json Versions

1 component(s)
Fixed Versions:
2.0.0
Product / Package Ecosystem Affected Versions Fixed Version
unicode-json
npm
< 2.0.0
2.0.0

References

Frequently Asked Questions

What is CVE-2016-10610?
CVE-2016-10610 is a security vulnerability in Unicode json involving Downloads Resources over HTTP in unicode-json under CWE-311: Missing Encryption of Sensitive Data.
Which Unicode json versions are affected?
Affected versions include releases prior to 2.0.0 across affected packages: unicode-json.
What version fixes CVE-2016-10610?
Upgrading to 2.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is unicode-json affected?
Yes, unicode-json is affected in releases prior to 2.0.0. Upgrade your dependency to 2.0.0 or later.
What CWE is associated with CVE-2016-10610?
CVE-2016-10610 is classified under CWE-311: Missing Encryption of Sensitive Data (The product does not encrypt sensitive or critical information before storage or transmission.).
How can I check npm dependencies for CVE-2016-10610?
Run the dependency tree command: 'npm ls unicode-json'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hw4r-xr38-hm8j",
  "modified" : "2021-01-08T18:39:28Z",
  "published" : "2019-02-18T23:47:59Z",
  "aliases" : [ "CVE-2016-10610" ],
  "summary" : "Downloads Resources over HTTP in unicode-json",
  "details" : "Affected versions of `unicode-json` insecurely downloads resources over HTTP. \n\nIn scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.\n\n\n## Recommendation\n\nInstall version 2.0.0 or greater.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "unicode-json"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2016-10610"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-hw4r-xr38-hm8j"
  }, {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/206"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-311" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-06-16T21:41:11Z",
    "nvd_published_at" : null
  }
}