dbcve.org
DigdashApplication

CVE-2020-13651

HIGH · 7.8 CVSS v3.1 Published 2020-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DigDash Enterprise allows authenticated users to supply data used to generate JNLP (Java Web Start) files. An attacker can provide a malicious URL in this process, causing the client to download a rogue JNLP file that specifies malicious JAR archives. These JARs execute with full privileges on the client machine, enabling arbitrary code execution.

MitigationUpdate DigDash to the patched versions (2018R2 p20200528, 2019R1 p20200421, or 2019R2 p20200430). Additionally, disable Java Web Start/Java Plugin in browsers and educate users about the risks of running untrusted JNLP applications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DigdashApplication
Affected:= 2018r2= 2019r1= 2019r2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify DigDash Enterprise installation exists
    Check for DigDash installation directories (commonly in C:\Program Files\DigDash or /opt/digdash), or look for the DigDash web application running on common ports (8080, 8443, or your configured port). Check Windows Services or Linux processes for DigDash services.
    Affected if DigDash Enterprise is installed and running in the environment
  2. Identify the installed DigDash version
    Locate version information in the DigDash installation: check for a version.txt, about page in the web interface (usually /digdash//about or similar), or check version files in the installation directory. Compare against affected versions: 2018r2, 2019r1, or 2019r2.
    Affected if The installed version is exactly 2018r2, 2019r1, or 2019r2 (without the referenced patches p20200528, p20200421, or p20200430)
  3. Check for JNLP export/generation functionality
    Examine DigDash web application for JNLP export or Java Web Start features. Look for menu options allowing users to export or generate JNLP files. Check the application's feature configuration or documentation for JNLP-related modules.
    Affected if The JNLP generation/export feature is present and accessible to authenticated users
  4. Verify Java Web Start or Java Plugin availability on client systems
    On client machines that connect to DigDash, check browser settings and installed plugins for Java Web Start (JNLP) or Java Plugin. In Windows, check Control Panel > Java > Security, or examine browser extension settings for Java-related plugins.
    Affected if Java Web Start or the Java Plugin is enabled in browsers on client systems that would open JNLP files from DigDash

A user is affected if they run DigDash Enterprise versions 2018r2, 2019r1, or 2019r2 (unpatched), have the JNLP generation feature accessible to authenticated users, and users have Java Web Start enabled in their browsers to open generated JNLP files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update DigDash to the patched versions (2018R2 p20200528, 2019R1 p20200421, or 2019R2 p20200430). Additionally, disable Java Web Start/Java Plugin in browsers and educate users about the risks of running untrusted JNLP applications.

Fix this in Digdash Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-13651 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data