Code execution via attacker-controlled JNLP URL
Published Jun 15, 2020 · Updated Aug 4, 2024
Content injection in DigDash Enterprise allows remote attackers to execute malicious JAR files on targeted client computers. The unauthenticated ddserver parameter is copied into the generated digdash.jnlp codebase, causing Java to retrieve an attacker-hosted JNLP that names a malicious JAR. A targeted user must launch the generated JNLP; its all-permissions declaration runs the downloaded code with full client privileges.
Summary
What happened
Content injection in DigDash Enterprise allows remote attackers to execute malicious JAR files on targeted client computers. The unauthenticated ddserver parameter is copied into the generated digdash.jnlp codebase, causing Java to retrieve an attacker-hosted JNLP that names a malicious JAR. A targeted user must launch the generated JNLP; its all-permissions declaration runs the downloaded code with full client privileges.
The record
- CVE
- CVE-2020-13651
- Published
- Jun 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-829, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 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
- Bishop Fox malicious JNLP proof of conceptfunctional · demonstrated
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