CVE-2019-16539: Missing permission check in Jenkins Support Core Plugin

Summary

24/05/2022
Yes i
Moderate
6.5

CVE-2019-16539: Missing permission check in Jenkins Support Core Plugin. Affects org.jenkins-ci.plugins:support-core versions < 2.64. Fixed in 2.64. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Jenkins Support Core Plugin is a component of the Jenkins automation server that provides core support functionality. It allows users to generate and manage support bundles, which contain diagnostic information for troubleshooting purposes. The plugin is widely used in various software development and continuous integration environments.

Vulnerability Detail

The Jenkins Support Core Plugin version 2.63 and earlier suffer from a missing permission check vulnerability. Attackers with Overall/Read permission can exploit this vulnerability to delete support bundles. This can lead to unauthorized access to sensitive diagnostic information and potential disruption of troubleshooting processes.

How To Fix

Latest published version: 1865.v45d40b_778b_cb_ as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.64

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to the latest version of the Jenkins Support Core Plugin.

Conclusion

The missing permission check vulnerability in Jenkins Support Core Plugin version 2.63 and earlier can allow attackers with Overall/Read permission to delete support bundles. To mitigate this vulnerability, users should upgrade to version 2.64 or later. For further assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:support-core →

Share this vulnerability

FAQ

This vulnerability allows attackers with Overall/Read permission to delete support bundles, potentially compromising diagnostic information and disrupting troubleshooting processes.

Users of Jenkins Support Core Plugin versions 2.63 and earlier are affected by this vulnerability.

There are no known public exploits for this vulnerability at the time of this report.

Yes, users should upgrade to Jenkins Support Core Plugin version 2.64 or later to fix this vulnerability.

No, upgrading to the fixed version is the recommended solution to mitigate this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:support-core.

How To Fix

Latest published version: 1865.v45d40b_778b_cb_ as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.64

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback