David Fiser

**Name of the Vulnerable Software and Affected Versions** Wondershare Repairit version 6.5.2 Wondershare Repairit (affected versions not specified) **Description** The software contains an authentication bypass issue stemming from incorrect permission assignments within a storage account token. This allows remote attackers to bypass authentication without needing to log in. The flaw enables attackers to access the system by exploiting the permissions associated with the token. Multiple reports indicate the potential for supply chain risks, including the ability to swap AI models. No estimated number of affected devices or real-world incidents beyond the discovery of the flaw have been reported. **Recommendations** 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** Wondershare Repairit (affected versions not specified) **Description** The software contains an authentication bypass due to incorrect permission assignment of SAS tokens. This allows unauthorized access. **Recommendations** 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: NVIDIA Riva (affected versions not specified) Description: The issue is related to improper access control, which could be exploited to cause data tampering or denial of service. Recommendations: 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** NVIDIA Riva versions up to and including 2.18.0 **Description** The issue is related to improper access control, which could lead to escalation of privileges, data tampering, denial of service, or information disclosure. A successful exploit of this vulnerability might have significant consequences. The estimated number of potentially affected devices worldwide is not specified. There are reports of real-world incidents where this issue was exploited. **Recommendations** For versions up to and including 2.18.0, update to a newer version that addresses the improper access control issue to prevent potential data tampering and escalation risks. As a temporary workaround, consider restricting access to sensitive areas of the system to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Azure Service Fabric Container (affected versions not specified) **Description** The issue is related to the Azure Service Fabric Container and involves an elevation of privilege vulnerability. This vulnerability is associated with the WAagent daemon and its insecure management of privileges. Exploitation of this issue could allow an attacker to elevate their privileges. **Recommendations** 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 iceScrum Plugin version 1.1.4 and earlier **Description** The issue allows stored credentials to be stored unencrypted in job config.xml files on the Jenkins master. These credentials could be viewed by users with Extended Read permission or access to the master file system. **Recommendations** For Jenkins iceScrum Plugin version 1.1.4 and earlier, update to a version later than 1.1.4 to ensure credentials are properly encrypted.

**Name of the Vulnerable Software and Affected Versions** Jenkins NeoLoad Plugin versions 2.2.5 and earlier **Description** The issue concerns the storage of credentials in an unencrypted manner within the global configuration file and job config.xml files on the Jenkins master. This allows users with Extended Read permission or access to the master file system to view these credentials. **Recommendations** For Jenkins NeoLoad Plugin versions 2.2.5 and earlier, update to version 2.2.6 or later to resolve the issue of storing credentials unencrypted.

**Name of the Vulnerable Software and Affected Versions** Jenkins Sofy.AI Plugin (affected versions not specified) **Description** The issue concerns the storage of sensitive information by the Jenkins Sofy.AI Plugin. Specifically, it stores credentials and an API token unencrypted in job config.xml files on the Jenkins master or controller. This unencrypted storage allows users with Extended Read permission or access to the master or controller file system to view these sensitive details. There is no information provided about the estimated number of potentially affected devices or real-world incidents related to this issue. **Recommendations** 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 Extensive Testing Plugin (affected versions not specified) **Description** The issue concerns the storage of credentials in an unencrypted manner within job config.xml files on the Jenkins master. Users with Extended Read permission or access to the master file system can view these credentials. **Recommendations** 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 Fortify on Demand Plugin (affected versions not specified) **Description** The issue concerns the storage of credentials in an unencrypted manner within job config.xml files on the Jenkins master or controller. These credentials can be accessed by users who have Extended Read permission or those with direct access to the master or controller file system. **Recommendations** 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 ElasticBox CI Plugin (affected versions not specified) **Description** The issue concerns the storage of credentials in an unencrypted manner within the global config.xml configuration file on the Jenkins master. This allows users with access to the master file system to view these credentials. **Recommendations** 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 SOASTA CloudTest Plugin (affected versions not specified) **Description** The issue concerns the storage of credentials in an unencrypted manner within the global configuration file on the Jenkins master or controller. Specifically, the credentials are stored in the `com.soasta.jenkins.CloudTestServer.xml` file. This could allow users with access to the Jenkins controller file system to view these credentials. There is no information provided about the estimated number of potentially affected devices or real-world incidents where this issue was exploited. **Recommendations** 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 View26 Test-Reporting Plugin (affected versions not specified) **Description** The issue concerns the storage of sensitive information in an unencrypted manner. Specifically, the Jenkins View26 Test-Reporting Plugin stores credentials and an access token unencrypted in job config.xml files on the Jenkins master or controller. This allows users with Extended Read permission or access to the master or controller file system to view these sensitive details. **Recommendations** 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 Delphix Plugin (affected versions not specified) **Description** The issue concerns the storage of credentials in an unencrypted manner within the global configuration file of the Jenkins master. This allows users with access to the master file system to view these credentials. **Recommendations** 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 Dingding Plugin (affected versions not specified) **Description** The issue concerns the storage of credentials in an unencrypted manner in job config.xml files on the Jenkins master. These credentials can be accessed by users with Extended Read permission or those who have access to the master file system. **Recommendations** 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 Google Cloud Messaging Notification Plugin version 1.0 and earlier **Description** The issue concerns the storage of credentials in an unencrypted manner within the global configuration file on the Jenkins master. This allows users with access to the master file system to view these credentials. **Recommendations** For Jenkins Google Cloud Messaging Notification Plugin version 1.0 and earlier, consider removing or encrypting the stored credentials in the global configuration file to prevent unauthorized access. As a temporary workaround, restrict access to the Jenkins master file system to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Jenkins TestLink Plugin versions 3.16 and earlier **Description** The issue concerns the storage of credentials in an unencrypted manner within the global configuration file on the Jenkins master or controller. Specifically, the credentials are stored in the hudson.plugins.testlink.TestLinkBuilder.xml file. This allows users with access to the Jenkins controller or master file system to view these credentials. There is no information available about the estimated number of potentially affected devices or real-world incidents where this issue was exploited. **Recommendations** For Jenkins TestLink Plugin versions 3.16 and earlier: At the moment, there is no information about a newer version that contains a fix for this vulnerability. As a temporary workaround, consider restricting access to the hudson.plugins.testlink.TestLinkBuilder.xml file to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Jenkins eggPlant Plugin version 2.2 and earlier **Description** The issue allows credentials to be stored unencrypted in job config.xml files on the Jenkins master. These credentials can be viewed by users with Extended Read permission or those who have access to the master file system. **Recommendations** For Jenkins eggPlant Plugin version 2.2 and earlier, consider restricting access to the master file system and limiting Extended Read permissions to minimize the risk of credentials exposure until a fix is available.

**Name of the Vulnerable Software and Affected Versions** Jenkins PegDown Formatter Plugin versions 1.3 and earlier **Description** A stored cross-site scripting issue allows attackers who can edit descriptions and other fields to insert links with the `javascript:` scheme into the Jenkins UI. The PegDown Formatter Plugin uses the PegDown library to render Markdown formatted descriptions and advertises disabling of HTML to prevent cross-site scripting, but it does not prevent the use of the `javascript:` scheme in URLs for links. This results in an exploitable issue by users able to configure entities with descriptions that are rendered by the configured markup formatter. **Recommendations** For Jenkins PegDown Formatter Plugin versions 1.3 and earlier, as a temporary workaround, consider disabling the plugin until a patch is available. Restrict access to the plugin's functionality to minimize the risk of exploitation. Avoid using the plugin to render descriptions or similar properties that could be used to insert malicious links. At the moment, there is no information about a newer version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** Jenkins File System SCM Plugin version 2.1 and earlier **Description** The issue allows attackers who can configure jobs in Jenkins to read the contents of any file on the Jenkins master. This is due to an arbitrary file read vulnerability. **Recommendations** For Jenkins File System SCM Plugin version 2.1 and earlier, update to a version later than 2.1 to resolve the issue.