Support CoreApplication · Jenkins
CVE-2019-16540
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 · uneditedA path traversal vulnerability in Jenkins Support Core Plugin 2.63 and earlier allows attackers with Overall/Read permission to delete arbitrary files on the Jenkins master.
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 confidenceA path traversal vulnerability in Jenkins Support Core Plugin versions 2.63 and earlier allows authenticated users with only Overall/Read permission to delete arbitrary files on the Jenkins master file system. The vulnerability stems from insufficient input validation in file deletion functionality, enabling attackers to traverse directories using '../' sequences.
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
Support CoreApplication
<= 2.63CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Jenkins Support Core Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or check the $JENKINS_HOME/plugins/ directory for a folder named support-core or similar, or query the Jenkins REST API at /pluginManager/plugins/jsonAffected if The plugin appears in the list of installed plugins
-
Identify the installed version of Support Core PluginIn the installed plugins list, locate the Support Core Plugin entry and note the version number displayed in the Version columnAffected if The version is 2.63 or earlier (e.g., 2.63, 2.62, 2.60, etc.)
-
Confirm Overall/Read permission is granted to usersNavigate to Manage Jenkins > Manage Users and then check authorization settings under Manage Jenkins > Configure Global Security. Verify which users or groups have the Overall/Read permission enabledAffected if Any user account or group has Overall/Read permission enabled, especially untrusted or guest accounts
-
Check for suspicious file deletion activity in logsReview Jenkins logs (typically $JENKINS_HOME/logs/ or via Manage Jenkins > System Log) for entries containing patterns like 'deleteFile', 'file deletion', or frequent '../' path traversal attempts targeting files outside expected directoriesAffected if Log entries show file deletions occurring in unexpected directories or anomalous patterns
A user is affected if Jenkins Support Core Plugin version 2.63 or earlier is installed and Overall/Read permission is enabled for any user, regardless of how restricted their other permissions may be.
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 dataUpdate Jenkins Support Core Plugin to version 2.64 or later to receive the patched code. If immediate updating is not possible, restrict Overall/Read permission to only trusted users and monitor for suspicious file deletion activity.
Fix this in Support Core
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16540 — 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-2019-16540 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