Vincent Lardet

**Name of the Vulnerable Software and Affected Versions:** Jenkins Sensedia Api Platform Tools Plugin version 1.0 **Description:** The Jenkins Sensedia Api Platform Tools Plugin stores the Sensedia API Manager integration token unencrypted in its global configuration file on the Jenkins controller. This allows users with access to the Jenkins controller file system to view the token. **Recommendations:** Ensure the Jenkins controller file system is adequately secured to prevent unauthorized access.

**Name of the Vulnerable Software and Affected Versions:** Jenkins ReadyAPI Functional Testing Plugin versions 1.11 and earlier **Description:** The Jenkins ReadyAPI Functional Testing Plugin does not properly mask sensitive information such as SLM License Access Keys, client secrets, and passwords on the job configuration form. This increases the risk of unauthorized observation and capture of these credentials. **Recommendations:** Upgrade to Jenkins ReadyAPI Functional Testing Plugin version 1.12 or later.

**Name of the Vulnerable Software and Affected Versions:** Jenkins Dead Man's Snitch Plugin version 0.1 **Description:** The Jenkins Dead Man's Snitch Plugin version 0.1 stores Dead Man's Snitch tokens unencrypted in `job config.xml` files on the Jenkins controller. This allows users with Item/Extended Read permission or access to the Jenkins controller file system to view the tokens. **Recommendations:** Update to a newer version of the Jenkins Dead Man's Snitch Plugin that addresses this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions:** Jenkins VAddy Plugin versions prior to 1.2.9 **Description:** The Jenkins VAddy Plugin stores VAddy API Auth Keys unencrypted in job config.xml files on the Jenkins controller. These keys are accessible to users with Item/Extended Read permission or those with access to the Jenkins controller file system. **Recommendations:** Upgrade to Jenkins VAddy Plugin version 1.2.9 or later.

### Name of the Vulnerable Software and Affected Versions: Jenkins VAddy Plugin versions 1.2.8 and earlier ### Description: The Jenkins VAddy Plugin does not mask Vaddy API Auth Keys displayed on the job configuration form, potentially allowing attackers to observe and capture them. ### Recommendations: Update to a newer version of the Jenkins VAddy Plugin to address this issue.

**Name of the Vulnerable Software and Affected Versions:** Jenkins ReadyAPI Functional Testing Plugin versions 1.11 and earlier **Description:** The Jenkins ReadyAPI Functional Testing Plugin stores sensitive information, including SLM License Access Keys, client secrets, and passwords, in unencrypted format within job config.xml files on the Jenkins controller. This allows users with Item/Extended Read permission or file system access to view these credentials. **Recommendations:** Versions prior to 1.11: Ensure that access to the Jenkins controller file system is restricted to authorized personnel only. Limit Item/Extended Read permissions to only those users who require access to job configurations.

Name of the Vulnerable Software and Affected Versions: Jenkins Cadence vManager Plugin versions 4.0.1-286.v9e25a 740b a 48 and earlier Description: A cross-site request forgery (CSRF) issue allows attackers to connect to an attacker-specified URL using an attacker-specified `username` and `password`. This can be exploited by attackers to perform unauthorized actions. Recommendations: For Jenkins Cadence vManager Plugin versions 4.0.1-286.v9e25a 740b a 48 and earlier, consider disabling the plugin until a patch is available to prevent exploitation. Restrict access to sensitive URLs and credentials to minimize the risk of unauthorized connections.

**Name of the Vulnerable Software and Affected Versions** Jenkins Cadence vManager Plugin versions 4.0.1-286.v9e25a 740b a 48 and earlier **Description** The issue is related to missing permission checks in the Jenkins Cadence vManager Plugin, which allows attackers with Overall/Read permission to connect to an attacker-specified URL using an attacker-specified username and password. **Recommendations** For Jenkins Cadence vManager Plugin versions 4.0.1-286.v9e25a 740b a 48 and earlier, consider disabling the plugin until a patch is available to prevent attackers from connecting to attacker-specified URLs using attacker-specified credentials. Restrict access to the plugin to minimize the risk of exploitation. Avoid using the plugin with Overall/Read permission until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Jenkins AsakusaSatellite Plugin versions 0.1.1 and earlier **Description** The issue concerns the storage of AsakusaSatellite API keys in an unencrypted manner within job config.xml files on the Jenkins controller. This allows users with Item/Extended Read permission or access to the Jenkins controller file system to view these keys. **Recommendations** For Jenkins AsakusaSatellite Plugin versions 0.1.1 and earlier, consider restricting access to the Jenkins controller file system and limiting Item/Extended Read permissions to minimize exposure of the unencrypted AsakusaSatellite API keys until a fix is available.

**Name of the Vulnerable Software and Affected Versions** Jenkins Cadence vManager Plugin versions 4.0.0-282.v5096a c2db 275 and earlier **Description** The issue concerns the storage of Verisium Manager vAPI keys in an unencrypted form within job config.xml files on the Jenkins controller. These keys can be accessed by users who have Extended Read permission or direct access to the Jenkins controller file system. **Recommendations** For versions 4.0.0-282.v5096a c2db 275 and earlier, consider restricting access to the Jenkins controller file system and limiting Extended Read permissions to minimize exposure of the unencrypted vAPI keys until a fix is available.