Jenkins Credential Exposure via Unencrypted POST Config.xml

Compliance Impact

This vulnerability results in secrets being stored unencrypted in job configuration files on the Jenkins controller, where they can be accessed by users with certain permissions or by accessing the file system.

Storing sensitive information unencrypted can lead to unauthorized disclosure of confidential data, which may violate data protection requirements in standards and regulations such as GDPR and HIPAA that mandate protection of sensitive information.

Therefore, this vulnerability could negatively impact compliance with these regulations by failing to adequately protect sensitive secrets.

Useful 0 Not Useful 0

Executive Summary

This vulnerability affects Jenkins versions 2.567 and earlier, as well as LTS 2.555.2 and earlier. It occurs because secrets submitted via POST requests to config.xml are not encrypted before being stored in the job configuration files on the Jenkins controller.

As a result, these secrets are stored in plaintext within the job config.xml files, making them accessible to users who have Item/Extended Read permissions or those who can access the Jenkins controller's file system.

Useful 0 Not Useful 0

Impact Analysis

The vulnerability can lead to unauthorized disclosure of sensitive information, such as secrets or credentials, because they are stored unencrypted in job configuration files.

Users with certain permissions or access to the Jenkins controller file system could view these secrets, potentially leading to security breaches or misuse of confidential data.

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate this vulnerability, you should upgrade Jenkins to a version later than 2.567 or LTS later than 2.555.2 where this issue is resolved.

Additionally, restrict access to users with Item/Extended Read permission and limit access to the Jenkins controller file system to trusted administrators only, to prevent unauthorized viewing of unencrypted secrets.

Useful 0 Not Useful 0