Pod code execution via exposed JDWP listener
Published Mar 18, 2020 · Updated Aug 4, 2024
Missing authentication in ONAP SDC through Dublin allows remote attackers with pod-network access to execute code through exposed JDWP. The demo-sdc-sdc-wfd-fe pod exposes an unauthenticated Java Debug Wire Protocol listener on TCP port 7000, granting debugger control over its Java process. The attacker must already reach pod-to-pod traffic in an OOM deployment; successful access executes arbitrary code inside that pod.
Summary
What happened
Missing authentication in ONAP SDC through Dublin allows remote attackers with pod-network access to execute code through exposed JDWP. The demo-sdc-sdc-wfd-fe pod exposes an unauthenticated Java Debug Wire Protocol listener on TCP port 7000, granting debugger control over its Java process. The attacker must already reach pod-to-pod traffic in an OOM deployment; successful access executes arbitrary code inside that pod.
The record
- CVE
- CVE-2019-12119
- Published
- Mar 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-306, T1055
- 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