CVE-2016-10524 json
Denial of Service and Content Injection in i18n-node-angular
published 8y ago modified 4mo ago also GHSA-97gv-3p2c-xw7j , EUVD-2019-0267
- cvss
- 8.2
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
i18n-node-angular is a module used to interact between i18n and angular without using additional resources. A REST API endpoint that is used for development in i18n-node-angular before 1.4.0 was not disabled in production environments a malicious user could fill up the server causing a Denial of Service or content injection.
Patch / fix
- npm i18n-node-angular 1.4.0
- i18n-node-angular_project i18n-node-angular 1.4.0
Is CVE-2016-10524 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
0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
| GitHub | 3.0 | 8.2 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | i18n-node-angular | <1.4.0 |
1.4.0 |
Affected products
- HackerOne i18n-node-angular node module
Classification
References
-
github.com
/oliversalzburg/i18n-node-angular/commit/877720d2d9bb90dc8233706e81ffa03f99fc9dc8
web, patch, third-party-advisory
-
nodesecurity.io
/advisories/80
broken-link, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2016-10524
advisory
-
github.com
/advisories/GHSA-97gv-3p2c-xw7j
advisory
-
github.com
/oliversalzburg/i18n-node-angular
package
-
npmjs.com
/advisories/80
web
Sources
- CVE List CVE-2016-10524
- GitHub Advisory GHSA-97gv-3p2c-xw7j
- NVD CVE-2016-10524
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.