CVE-2016-10529: Droppy No CSRF Validation Vulnerability

HIGH
Advisory Identifier: GHSA-rhvc-x32h-5526
Share
CWE-352
Published
Advisory Summary

CVE-2016-10529 is a HIGH no csrf validation vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Droppy libraries in the npm ecosystem. The issue involves no csrf validation in droppy. Remediation is available by upgrading affected packages to version 3.5.0.

CVE-2016-10529 at a Glance

CVE Identifier CVE-2016-10529
GHSA Identifier GHSA-rhvc-x32h-5526
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Droppy
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2016-10529

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

droppy fixed: 3.5.0 
npm install droppy@3.5.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 droppy

How to Check if You Are Affected

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

npm ls droppy

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

Note: The npm ls droppy 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-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Droppy, 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 `droppy` are vulnerable to cross-site socket forgery. The package does not perform verification for cross-domain websocket requests, and as a result, an attacker can create a web page that opens up a websocket connection on behalf of the user visiting the page. The attacker can then perform any action that the target user could, including adding a new admin account under their control, or deleting others. ## Recommendation Update to version 3.5.0 or later.

CVE-2016-10529 Affected Droppy Versions

1 component(s)
Fixed Versions:
3.5.0
Product / Package Ecosystem Affected Versions Fixed Version
droppy
npm/droppy
npm
< 3.5.0
3.5.0

References

NVD — CVE-2016-10529 NVD
https://nvd.nist.gov/vuln/detail/CVE-2016-10529
GitHub Advisory / Wiki ADVISORY
https://github.com/advisories/GHSA-rhvc-x32h-5526
www.npmjs.com/advisories/91 WEB
https://www.npmjs.com/advisories/91

Frequently Asked Questions

What is CVE-2016-10529?
CVE-2016-10529 is a security vulnerability in Droppy involving No CSRF Validation in droppy under CWE-352: Cross-Site Request Forgery (CSRF).
Which Droppy versions are affected?
Affected versions include releases prior to 3.5.0 across affected packages: droppy.
What version fixes CVE-2016-10529?
Upgrading to 3.5.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is droppy affected?
Yes, droppy is affected in releases prior to 3.5.0. Upgrade your dependency to 3.5.0 or later.
What CWE is associated with CVE-2016-10529?
CVE-2016-10529 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check npm dependencies for CVE-2016-10529?
Run the dependency tree command: 'npm ls droppy'. 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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rhvc-x32h-5526",
  "modified" : "2020-08-31T18:10:30Z",
  "published" : "2019-02-18T23:39:32Z",
  "aliases" : [ "CVE-2016-10529" ],
  "summary" : "No CSRF Validation in droppy",
  "details" : "Affected versions of `droppy`  are vulnerable to cross-site socket forgery. The package does not perform verification for cross-domain websocket requests, and as a result, an attacker can create a web page that opens up a websocket connection on behalf of the user visiting the page. The attacker can then perform any action that the target user could, including adding a new admin account under their control, or deleting others.\n\n\n## Recommendation\n\nUpdate to version 3.5.0 or later.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "droppy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.5.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2016-10529"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-rhvc-x32h-5526"
  }, {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/91"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-06-16T21:55:03Z",
    "nvd_published_at" : null
  }
}