CVE-2019-12120
First published: Wed Mar 18 2020(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Onap Open Network Automation Platform | >=3.0.0<4.0.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-12120?
CVE-2019-12120 is a high-severity vulnerability that allows unauthenticated attackers to execute arbitrary code.
How do I fix CVE-2019-12120?
To mitigate CVE-2019-12120, ensure that access to port 8000 is restricted and consider applying security patches provided by ONAP.
Who is affected by CVE-2019-12120?
All ONAP Operations Manager (OOM) setups are affected by CVE-2019-12120, particularly those using the ONAP VNFSDK.
What type of attack does CVE-2019-12120 enable?
CVE-2019-12120 enables an unauthenticated attacker to execute arbitrary code within the affected pod.
Which versions of ONAP are vulnerable to CVE-2019-12120?
CVE-2019-12120 affects ONAP Open Network Automation Platform versions between 3.0.0 and 4.0.0.
- collector/nvd-index
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- agent/author
- agent/severity
- agent/weakness
- agent/remedy
- agent/softwarecombine
- agent/first-publish-date
- agent/description
- agent/event
- agent/tags
- agent/source
- vendor/onap
- canonical/onap open network automation platform
- version/onap open network automation platform/3.0.0