Unauthenticated service access via exposed CLI port
Published Mar 19, 2020 · Updated Aug 4, 2024
Missing authentication in ONAP CLI through Dublin allows remote attackers to gain full service access through TCP port 30271. OOM publishes the CLI API or UI on that port without an authentication check, so any client reaching it receives the service's full functionality. Every OOM setup is exposed when the port is network-reachable; the vendor has not further bounded the operations available under full access.
Summary
What happened
Missing authentication in ONAP CLI through Dublin allows remote attackers to gain full service access through TCP port 30271. OOM publishes the CLI API or UI on that port without an authentication check, so any client reaching it receives the service's full functionality. Every OOM setup is exposed when the port is network-reachable; the vendor has not further bounded the operations available under full access.
The record
- CVE
- CVE-2019-12130
- Published
- Mar 19, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo