CVE-2018-1000412: Jenkins Jira Plugin Incorrect Authorization vulnerability
Summary
CVE-2018-1000412: Jenkins Jira Plugin Incorrect Authorization vulnerability. Affects org.jenkins-ci.plugins:jira versions < 3.0.2. Fixed in 3.0.2. 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
The Jenkins Jira Plugin is a plugin for the Jenkins automation server that allows integration with Jira, a popular issue tracking and project management tool. It provides functionality to connect Jenkins to Jira instances and perform various actions, such as creating issues, updating issues, and retrieving issue information. The plugin is commonly used in software development and continuous integration workflows to streamline the management of issues and track their progress. However, versions 3.0.1 and earlier of the plugin are vulnerable to an improper authorization issue.
Vulnerability Detail
The vulnerability in the Jenkins Jira Plugin allows attackers with Overall/Read access to have Jenkins connect to a URL specified by the attacker using credentials IDs obtained through another method. This can lead to the capture of credentials stored in Jenkins. The issue is present in the JiraSite.java file of the plugin. In version 3.0.2, the form validation method has been updated to require POST requests and specific permissions (Overall/Administer or Item/Configure) to mitigate the vulnerability. The vulnerability has a CVSS score of 4.2, indicating a moderate severity level.
How To Fix
Latest published version: 3.22 as of 22 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
3.0.2
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
If upgrading to version 3.0.2 is not immediately possible, a temporary workaround is to restrict access to the Jenkins instance and ensure that only trusted users with appropriate permissions have Overall/Read access. Additionally, it is recommended to monitor the Jenkins logs for any suspicious activity and regularly review and rotate the stored credentials to minimize the potential impact of the vulnerability.
Conclusion
The Jenkins Jira Plugin versions 3.0.1 and earlier are vulnerable to an improper authorization issue that can allow attackers to capture credentials stored in Jenkins. It is crucial to upgrade to version 3.0.2 or later to mitigate the vulnerability. Restricting access to the Jenkins instance and monitoring for suspicious activity are recommended as temporary measures. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:jira →
FAQ
The vulnerability allows attackers with Overall/Read access to connect Jenkins to an attacker-specified URL using attacker-specified credentials IDs, potentially leading to the capture of credentials stored in Jenkins.
Users of Jenkins Jira Plugin versions 3.0.1 and earlier are affected by this vulnerability.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins instance is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is important to promptly apply the recommended fixes to mitigate the risk.
For more information about this vulnerability, you can refer to the CVE-2018-1000412 entry or contact the Jenkins Jira Plugin maintainers.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:jira.