CVE-2020-13651: An issue was discovered in DigDash 2018R2 before p20200528, 2019R1 before p20200421, and 2019R2 before p202004

This month

HIGH 7.8DOWNGRADE

CVE-2020-13651 is a high-severity flaw (CVSS 7.8) affecting digdash. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in DigDash 2018R2 before p20200528, 2019R1 before p20200421, and 2019R2 before p20200430. It allows a user to provide data that will be used to generate the JNLP file used by a client to obtain the right Java application. By providing an attacker-controlled URL, the client will obtain a rogue JNLP file specifying the installation of malicious JAR archives and executed with full privileges on the client computer.

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-829
Published	2020-06-15
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: digdash

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-06-15 19:15 UTCPublished CVE record published
2026-06-17 02:53 UTCUpdated Record last modified

digdash digdash DOWNGRADE

Affected: 2018r2 · 2019r1 · 2019r2

Fixed in: no fixed release known

Safe to downgrade to: a release before 2018r2

1. Check installed version

apt-cache policy digdash || rpm -q digdash || digdash --version

2. No fixed release: DOWNGRADE to a release before 2018r2 (Debian / Ubuntu)

apt-cache madison digdash sudo apt install digdash=<VERSION_BEFORE_2018r2> sudo apt-mark hold digdash

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list digdash sudo dnf downgrade digdash-<VERSION_BEFORE_2018r2> sudo dnf versionlock add digdash

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-13651?

digdash: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-13651 being exploited?

CVE-2020-13651 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-13651 affect?

CVE-2020-13651 affects digdash. Severity is high (CVSS 7.8). An issue was discovered in DigDash 2018R2 before p20200528, 2019R1 before p20200421, and 2019R2 before p20200430. It allows a user to provide data that will be used to generate the JNLP file used by a client to obtain the right Java applica

How urgent is CVE-2020-13651?

Priority 42/100. High severity

Software pages

Java vulnerabilities

Related CVEs

CVE-2020-13652 MEDIUM 6.1 DOWNGRADE An issue was discovered in DigDash 2018R2 before p20200528, 2019R1 before p20200528, 2019R2 before p20200430,
CVE-2020-13650 HIGH 7.5 DOWNGRADE An issue was discovered in DigDash 2018R2 before p20200210 and 2019R1 before p20200210

References

← Back to latest CVEs