CVE-2013-6372: Jenkins Subversion Plugin Vulnerability - Credentials Stored with Base64 Encoding
Summary
CVE-2013-6372: Jenkins Subversion Plugin Stores Credentials with Base64 Encoding. Affects org.jenkins-ci.plugins:subversion versions < 1.54. Fixed in 1.54. 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 Subversion Plugin is an extension for Jenkins that allows users to integrate Subversion version control into their CI/CD pipelines. It enables the management of source code repositories and facilitates automated builds and deployments. However, prior to version 1.54, the plugin had a significant security flaw that involved the insecure storage of credentials.
Vulnerability Detail
The vulnerability arises from the Subversion plugin's practice of storing sensitive credentials, such as passwords and SSH private keys, using base64 encoding in a file named subversion.credentials. This method of encoding is not secure, as it can be easily decoded by local users, potentially leading to unauthorized access to sensitive information and systems. The flaw is classified under CWE-326, which pertains to inadequate encryption of sensitive data.
How To Fix
Minimum fixed version
1.54
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
As a temporary workaround, consider restricting access to the subversion.credentials file to limit exposure. You can change the file permissions using the following command:
chmod 600 /path/to/subversion.credentials
This will ensure that only the owner can read and write to the file.
Conclusion
The Jenkins Subversion Plugin vulnerability (CVE-2013-6372) poses a significant risk due to the insecure storage of credentials. It is crucial to update to version 1.54 or later to mitigate this risk. Implementing temporary workarounds can help protect sensitive information until an update can be applied.
See every vulnerability recorded for org.jenkins-ci.plugins:subversion →
FAQ
Local users can decode the base64-encoded credentials, potentially gaining unauthorized access to sensitive systems and data.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Yes, the vulnerability is fixed in version 1.54 of the Subversion plugin. Updating to this version will resolve the issue.
Consider implementing file permission restrictions as a temporary workaround to limit access to the credentials file.
Vulert monitors and alerts for open-source vulnerabilities in your software using just the pom.xml file, providing real-time insights without requiring code access or installation.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:subversion.
