dbcve.org
Keepass DxApplication · Keepassdx

CVE-2018-1000835

CRITICAL · 10.0 CVSS v3.1 Published 2018-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
KeePassDX version <= 2.5.0.0beta17 contains a XML External Entity (XXE) vulnerability in kdbx file parser that can result in Disclosure of confidential data, denial of service, SSRF, port scanning.

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

KeePassDX versions 2.5.0.0beta17 and earlier contain an XML External Entity (XXE) vulnerability in the kdbx file parser. This allows malicious kdbx files to embed external XML entity references that can be processed during parsing, enabling disclosure of local files, denial of service, SSRF attacks, or internal port scanning.

MitigationUpgrade KeePassDX to a version newer than 2.5.0.0beta17, which includes proper XXE protection in the kdbx XML parser. Until then, avoid opening untrusted kdbx files.

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
Keepass DxApplication
Affected:= 2.5.0.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify KeePassDX installation and version
    Open KeePassDX app and navigate to the About or Settings section to view the installed version number, or check your device's app installer (Google Play Store, F-Droid, or iOS App Store) for the installed version
    Affected if Version is 2.5.0.0 or any beta/alpha release prior to and including 2.5.0.0beta17
  2. Confirm kdbx file parsing is in use
    Determine if you use KeePassDX to open .kdbx password database files, which is the primary function of the application
    Affected if You open or intend to open kdbx files with this version of KeePassDX
  3. Compare your version against affected range
    Compare the installed version number to the affected range: 2.5.0.0beta17 and earlier, including version 2.5.0.0
    Affected if Your installed version is 2.5.0.0 or any version up to and including 2.5.0.0beta17

You are affected if KeePassDX version 2.5.0.0beta17 or earlier (including 2.5.0.0) is installed and you open kdbx files, as the XXE vulnerability exists in the kdbx file parser of these versions.

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

Upgrade KeePassDX to a version newer than 2.5.0.0beta17, which includes proper XXE protection in the kdbx XML parser. Until then, avoid opening untrusted kdbx files.

Fix this in Keepass Dx Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000835 — 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-2018-1000835 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