i18n-node-angular up to 1.3.x on Node.js REST API Endpoint injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in i18n-node-angular up to 1.3.x on Node.js. The affected element is an unknown function of the component REST API Endpoint. The manipulation results in injection. This vulnerability is known as CVE-2016-10524. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in i18n-node-angular up to 1.3.x on Node.js (JavaScript Library). It has been classified as problematic. Affected is an unknown code block of the component REST API Endpoint. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on availability. CVE summarizes:
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.
The bug was discovered 01/25/2016. The weakness was published 05/31/2018 (Website). The advisory is available at github.com. This vulnerability is traded as CVE-2016-10524 since 10/29/2017. It is possible to launch the attack remotely. The requirement for exploitation is a authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1055 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 857 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.4.0 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.0
VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.2
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: i18n-node-angular 1.4.0
Patch: github.com
Timeline
01/25/2016 🔍10/29/2017 🔍
05/31/2018 🔍
05/31/2018 🔍
06/01/2018 🔍
03/17/2023 🔍
Sources
Advisory: 877720d2d9bb90dc8233706e81ffa03f99fc9dc8Status: Not defined
CVE: CVE-2016-10524 (🔍)
GCVE (CVE): GCVE-0-2016-10524
GCVE (VulDB): GCVE-100-118410
Entry
Created: 06/01/2018 09:28Updated: 03/17/2023 19:38
Changes: 06/01/2018 09:28 (58), 02/10/2020 09:49 (2), 03/17/2023 19:38 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.