ONAP VNFSDK up to Dublin demo-vnfsdk-vnfsdk code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in ONAP VNFSDK up to Dublin. Affected is an unknown function of the component demo-vnfsdk-vnfsdk. The manipulation leads to code injection. This vulnerability is traded as CVE-2019-12120. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to apply restrictive firewalling. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in ONAP VNFSDK up to Dublin and classified as critical. This issue affects an unknown code of the component demo-vnfsdk-vnfsdk. The manipulation with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in ONAP VNFSDK through Dublin. By accessing port 8000 of demo-vnfsdk-vnfsdk, an unauthenticated attacker (who already has access to pod-to-pod communication) may execute arbitrary code inside that pod. All ONAP Operations Manager (OOM) setups are affected.
The weakness was shared 03/18/2020. The identification of this vulnerability is CVE-2019-12120 since 05/15/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.
Addressing this vulnerability is possible by firewalling 8000.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
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: FirewallStatus: 🔍
0-Day Time: 🔍
Firewalling: 🔍
Timeline
05/15/2019 🔍03/18/2020 🔍
03/19/2020 🔍
04/17/2024 🔍
Sources
Advisory: jira.onap.orgStatus: Not defined
CVE: CVE-2019-12120 (🔍)
GCVE (CVE): GCVE-0-2019-12120
GCVE (VulDB): GCVE-100-151799
Entry
Created: 03/19/2020 08:17 AMUpdated: 04/17/2024 01:02 PM
Changes: 03/19/2020 08:17 AM (37), 03/19/2020 08:22 AM (17), 04/17/2024 01:02 PM (18)
Complete: 🔍
Cache ID: 244:702:40
No comments yet. Languages: en.
Please log in to comment.