CVE-2018-1000150: Jenkins Reverse Proxy Auth Plugin Information Disclosure
Summary
CVE-2018-1000150: An exposure of sensitive information vulnerability exists in Jenkins Reverse Proxy Auth Plugin 1.5 and older in ReverseProxySecurityRealm#authContext that allows attackers with local file system access to obtain a list o... Affects org.jenkins-ci.plugins:reverse-proxy-auth-plugin versions < 1.6.0. Fixed in 1.6.0. 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 Reverse Proxy Auth Plugin is a plugin for the Jenkins automation server that provides authentication and authorization capabilities through a reverse proxy. It allows users to log in to Jenkins using credentials from an external authentication system. This plugin is commonly used in Jenkins instances to enhance security and streamline user management.
Vulnerability Detail
The Reverse Proxy Auth Plugin in Jenkins versions 1.5 and older suffers from an exposure of sensitive information vulnerability. This vulnerability allows attackers with local file system access to obtain a list of authorities for logged-in users. The plugin's ReverseProxySecurityRealm#authContext stores a cache of granted authorities on disk, which can be accessed by an attacker. This information disclosure can potentially lead to further attacks or unauthorized access to sensitive resources.
How To Fix
Minimum fixed version
1.6.0
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 specific workaround provided for this vulnerability. The recommended solution is to upgrade to the latest version of the Reverse Proxy Auth Plugin.
Conclusion
The Jenkins Reverse Proxy Auth Plugin versions 1.5 and older suffer from an information disclosure vulnerability that allows attackers with local file system access to obtain a list of authorities for logged-in users. Upgrading to version 1.6.0 or newer of the plugin is recommended to mitigate this vulnerability. It is important to keep your Jenkins installation and its plugins up to date to ensure the security of your automation environment.
See every vulnerability recorded for org.jenkins-ci.plugins:reverse-proxy-auth-plugin →
FAQ
The vulnerability allows attackers with local file system access to obtain a list of authorities for logged-in users. This information can be used to gain unauthorized access to sensitive resources or perform further attacks.
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 open-source vulnerabilities in real-time.
There are no known public exploits for this vulnerability at the time of this report. However, it is important to apply the recommended fix to prevent potential exploitation.
Yes, there are several alternative authentication plugins available for Jenkins. Some popular options include the LDAP Plugin, GitHub Authentication Plugin, and Active Directory Plugin. It is recommended to evaluate the specific requirements of your Jenkins instance and choose an authentication plugin that best fits your needs.
For further support on vulnerability remediation and securing your Jenkins instance, you can reach out to info@devnack.com. Our team of experts will be happy to assist you.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:reverse-proxy-auth-plugin.
