Liquibase RunnerApplication · Jenkins
CVE-2020-2284
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 · uneditedJenkins Liquibase Runner Plugin 1.4.5 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
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 confidenceThe Jenkins Liquibase Runner Plugin versions 1.4.5 and earlier uses an XML parser that is not configured to prevent XML external entity (XXE) attacks. This allows attackers to exploit the parser by supplying malicious XML containing external entity references, potentially leading to disclosure of confidential data, denial of service, or server-side request forgery.
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
Liquibase RunnerApplication
<= 1.4.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Liquibase Runner Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the $JENKINS_HOME/plugins directory for liquibase-runner folderAffected if Plugin is not present in the plugin list or filesystem
-
Identify installed plugin versionCheck the version file inside $JENKINS_HOME/plugins/liquibase-runner/, or view the plugin details in Jenkins plugin managerAffected if Unable to determine version from plugin metadata
-
Compare version against affected rangeCheck if the installed version is 1.4.5 or earlier. The manifest or version file typically shows the exact version numberAffected if Version is 1.4.5 or lower (the vulnerable version range)
-
Confirm plugin is actively usedReview Jenkins jobs for pipeline steps or build triggers that invoke the liquibase-runner plugin, such as 'liquibaseRunner' or equivalent commands in job configurationsAffected if Plugin is installed and jobs reference Liquibase Runner to process database change logs
User is affected if Liquibase Runner Plugin version 1.4.5 or earlier is installed AND the plugin is used to process XML-based Liquibase change log files, as this triggers the unconfigured XML parser vulnerable to XXE attacks.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to Liquibase Runner Plugin version 1.4.6 or later, which configures the XML parser to prevent XXE attacks by disabling external entity processing.
Fix this in Liquibase Runner
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2284 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2284 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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