What is the severity of CVE-2019-16540?

CVE-2019-16540 is treated as a critical vulnerability due to its potential to allow unauthorized file deletion on the Jenkins master.

How do I fix CVE-2019-16540?

To fix CVE-2019-16540, upgrade the Jenkins Support Core Plugin to version 2.64 or later.

Who is affected by CVE-2019-16540?

Users of Jenkins Support Core Plugin versions 2.63 and earlier with Overall/Read permission are affected by CVE-2019-16540.

What does CVE-2019-16540 allow attackers to do?

CVE-2019-16540 allows attackers to delete arbitrary files from the Jenkins master.

What versions of Jenkins Support Core are vulnerable to CVE-2019-16540?

Jenkins Support Core Plugin versions up to and including 2.63 are vulnerable to CVE-2019-16540.

Vulnerability/
CVE-2019-16540

high

7.1

CWE

21/11/2019

24/5/2022

5/8/2024

CVE-2019-16540: Path Traversal

First published: Thu Nov 21 2019(Updated: )

A 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.

Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com

Affected Software	Affected Version	How to fix
Jenkins Support Core	<=2.63
maven/org.jenkins-ci.plugins:support-core	<=2.63	2.64

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-16540?
CVE-2019-16540 is treated as a critical vulnerability due to its potential to allow unauthorized file deletion on the Jenkins master.
How do I fix CVE-2019-16540?
To fix CVE-2019-16540, upgrade the Jenkins Support Core Plugin to version 2.64 or later.
Who is affected by CVE-2019-16540?
Users of Jenkins Support Core Plugin versions 2.63 and earlier with Overall/Read permission are affected by CVE-2019-16540.
What does CVE-2019-16540 allow attackers to do?
CVE-2019-16540 allows attackers to delete arbitrary files from the Jenkins master.
What versions of Jenkins Support Core are vulnerable to CVE-2019-16540?
Jenkins Support Core Plugin versions up to and including 2.63 are vulnerable to CVE-2019-16540.

collector/nvd-index
collector/nvd-api
collector/github-advisory-latest
alias/GHSA-2cxg-448h-4wxj
alias/CVE-2019-16540
collector/github-advisory
collector/nvd-cve
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/references
agent/severity
agent/last-modified-date
agent/weakness
agent/description
agent/event
agent/first-publish-date
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins support core
version/jenkins support core/2.63
package-manager/maven

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2019-16540?
CVE-2019-16540 is treated as a critical vulnerability due to its potential to allow unauthorized file deletion on the Jenkins master.
How do I fix CVE-2019-16540?
To fix CVE-2019-16540, upgrade the Jenkins Support Core Plugin to version 2.64 or later.
Who is affected by CVE-2019-16540?
Users of Jenkins Support Core Plugin versions 2.63 and earlier with Overall/Read permission are affected by CVE-2019-16540.
What does CVE-2019-16540 allow attackers to do?
CVE-2019-16540 allows attackers to delete arbitrary files from the Jenkins master.
What versions of Jenkins Support Core are vulnerable to CVE-2019-16540?
Jenkins Support Core Plugin versions up to and including 2.63 are vulnerable to CVE-2019-16540.