CVE-2016-10581 json
steroids downloads resources over HTTP
published 8y ago modified 4mo ago also GHSA-5m9c-634g-47vq , EUVD-2019-0227
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Steroids is PhoneGap on Steroids, providing native UI elements, multiple WebViews and enhancements for better developer productivity. steroids downloads zipped resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested tarball with an attacker controlled tarball if the attacker is on the network or positioned in between the user and the remote server.
Is CVE-2016-10581 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.66% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
| GitHub | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | steroids | <=4.1.27 |
no fix listed |
Affected products
- HackerOne steroids node module
Classification
References
-
nodesecurity.io
/advisories/168
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2016-10581
advisory
-
github.com
/AppGyver/steroids
package
-
github.com
/AppGyver/steroids/blob/master/package.json#L101
web
-
github.com
/AppGyver/steroids/blob/master/package.json#L103-L104
web
-
github.com
/AppGyver/steroids/blob/master/package.json#L74
web
-
npmjs.com
/advisories/168
web
Sources
- CVE List CVE-2016-10581
- GitHub Advisory GHSA-5m9c-634g-47vq
- NVD CVE-2016-10581
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.