CVE-2018-1999037: Jenkins Resource Disposer Plugin allows attacker to stop tracking specified resource
Summary
CVE-2018-1999037: Jenkins Resource Disposer Plugin allows attacker to stop tracking specified resource. Affects org.jenkins-ci.plugins:resource-disposer versions < 0.12. Fixed in 0.12. 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 Resource Disposer Plugin is a plugin for the Jenkins automation server that allows users to manage and dispose of resources used by Jenkins jobs. It provides a way to track and release resources such as files, connections, or other external resources after a job has completed. This plugin is commonly used in Jenkins environments to ensure efficient resource management and prevent resource leaks.
Vulnerability Detail
A vulnerability has been identified in the Jenkins Resource Disposer Plugin version 0.11 and earlier. The vulnerability exists in the AsyncResourceDisposer.java file, which is responsible for tracking and disposing of resources. Attackers can exploit this vulnerability to stop tracking a specified resource, leading to potential resource leaks and improper resource management. Additionally, the API endpoint used for this action did not require POST requests, making it susceptible to Cross-Site Request Forgery (CSRF) attacks. This vulnerability has been assigned the CVE identifier CVE-2018-1999037 and has a CVSS score of 3.1 (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L).
How To Fix
Minimum fixed version
0.12
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 the latest version is not immediately feasible, a temporary workaround can be implemented by restricting access to the vulnerable API endpoint. This can be done by configuring network firewalls or access control lists (ACLs) to block requests to the vulnerable endpoint. However, this workaround should only be considered as a temporary measure, and upgrading to the latest version is strongly recommended for a comprehensive fix.
Conclusion
The Jenkins Resource Disposer Plugin version 0.11 and earlier is vulnerable to a data modification and CSRF vulnerability. Upgrading to version 0.12 or later is recommended to fix the vulnerability and ensure secure resource tracking and disposal. Implementing the temporary workaround of restricting access to the vulnerable API endpoint can provide immediate protection until the upgrade is performed. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:resource-disposer →
FAQ
This vulnerability allows attackers to stop tracking a specified resource in the Jenkins Resource Disposer Plugin. This can lead to resource leaks, improper resource management, and potential security risks.
You can use the Vulert Playground at Vulert Scanner to check if your Jenkins environment is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the pom.xml file to analyze the software.
There are no known public exploits for this vulnerability at the time of this report. However, it is important to promptly apply the recommended fix to mitigate any potential risks.
Exploiting this vulnerability requires the attacker to have at least Low-level permissions in the Jenkins environment. However, upgrading to version 0.12 or later of the Jenkins Resource Disposer Plugin will require Overall/Administer permissions for the vulnerable API endpoint, further mitigating the risk.
For more information about this vulnerability, you can refer to the GitHub Security Advisory GHSA-63jg-5wv6-7ghv at https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-63jg-5wv6-7ghv/GHSA-63jg-5wv6-7ghv.json
