CVE-2019-10384: Cross-Site Request Forgery in Jenkins
Summary
CVE-2019-10384: Cross-Site Request Forgery in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
< 2.176.3
>= 2.177, < 2.192
Fixed in 2.176.3 or 2.192, depending on the release line you run. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
Jenkins is an open-source automation server that allows developers to build, test, and deploy their software projects. It is widely used in the software development industry for continuous integration and delivery. The vulnerable package in question is 'org.jenkins-ci.main:jenkins-core'. This package is a core component of Jenkins and provides essential functionality for its operation.
Vulnerability Detail
The vulnerability, identified as CVE-2019-10384, allows users to obtain Cross-Site Request Forgery (CSRF) tokens without an associated web session ID. This results in CSRF tokens that do not expire and can be used to bypass CSRF protection for the anonymous user. CSRF attacks can lead to unauthorized actions being performed on behalf of the user, potentially compromising the security and integrity of the Jenkins server. The vulnerability has a CVSS score of 8.8, indicating a high severity level.
How To Fix
Latest published version: 2.587 as of 22 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 2.176.32.176.3 -
>= 2.177, < 2.1922.192
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If upgrading the package is not immediately feasible, a temporary workaround is to manually invalidate the existing CSRF tokens and generate new ones. This can be done by restarting the Jenkins server or by triggering a configuration change that requires a CSRF token regeneration. However, this workaround is not a permanent solution and should be followed by upgrading to the latest secure version of the 'org.jenkins-ci.main:jenkins-core' package.
Conclusion
In conclusion, the CVE-2019-10384 vulnerability in Jenkins allows for Cross-Site Request Forgery attacks, potentially compromising the security of the server. It is crucial to upgrade the 'org.jenkins-ci.main:jenkins-core' package to the recommended versions or apply the provided workaround. Regularly monitoring for vulnerabilities using tools like Vulert can help ensure the ongoing security of your Jenkins server.
See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →
FAQ
Jenkins is an open-source automation server used for continuous integration and delivery of software projects.
A CSRF token is a security measure used to protect against Cross-Site Request Forgery attacks. It is a unique token generated for each user session and is required to perform certain actions on a web application.
This vulnerability can allow an attacker to perform unauthorized actions on behalf of the user, potentially compromising the security and integrity of the Jenkins server. It can lead to data breaches, unauthorized access, and other malicious activities.
You can use Vulert's playground (https://vulert.com/scanner) to check if your Jenkins server is affected by this vulnerability. Vulert provides real-time monitoring and alerts for open-source vulnerabilities in software, using just the pom.xml file.
For further support and assistance in remediating this vulnerability, you can reach out to info@devnack.com. Our team of experts will be happy to assist you.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
