Unauthenticated code execution via exposed JDWP port
Published Mar 18, 2020 · Updated Aug 4, 2024
Exposed JDWP in ONAP SDC through Dublin allows remote attackers with pod-network access to execute arbitrary code in the frontend pod. The demo-sdc-sdc-fe pod exposes its Java Debug Wire Protocol listener on port 6000 without authentication. Exploitation requires access to pod-to-pod communications and grants code execution only within the affected frontend pod.
Summary
What happened
Exposed JDWP in ONAP SDC through Dublin allows remote attackers with pod-network access to execute arbitrary code in the frontend pod. The demo-sdc-sdc-fe pod exposes its Java Debug Wire Protocol listener on port 6000 without authentication. Exploitation requires access to pod-to-pod communications and grants code execution only within the affected frontend pod.
The record
- CVE
- CVE-2019-12116
- Published
- Mar 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-306, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 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