Pwntester

**Name of the Vulnerable Software and Affected Versions** RSSHub versions prior to commit 64e00e7 **Description** RSSHub's `docker-test-cont.yml` workflow is vulnerable to Artifact Poisoning, which could have led to a full repository takeover. The workflow gets triggered when the `PR - Docker build test` workflow completes successfully and downloads an artifact uploaded by the triggering workflow. However, prior to commit 64e00e7, it did not validate the contents of the artifact, allowing a malicious actor to send a Pull Request that uploads a malicious `package.json` file with a script to run arbitrary code in the context of the privileged workflow. The `docker-test-cont.yml` workflow collects information about the Pull Request and sets labels depending on the PR body and sender. If the PR contains a `routes` markdown block, it sets the `TEST CONTINUE` environment variable to `true`. **Recommendations** For RSSHub versions prior to commit 64e00e7, update to a version that includes commit 64e00e7 to fix the underlying issue and prevent a possible repository takeover by malicious actors. As a temporary workaround, consider restricting access to the `docker-test-cont.yml` workflow to minimize the risk of exploitation. Avoid using the `package.json` file in the affected workflow until the issue is resolved.

Name of the Vulnerable Software and Affected Versions: arduino-esp32 (affected versions not specified) Description: The issue concerns multiple Poisoned Pipeline Execution (PPE) vulnerabilities in the arduino-esp32 CI, including code injection in the `tests results.yml` workflow and environment variable injection. These vulnerabilities have the potential for repository takeover and enable remote attacks with high impact. Users are advised to verify the contents of the downloaded artifacts. 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** Hoverfly (affected versions not specified) **Description** The `/api/v2/simulation` POST handler in Hoverfly allows users to create new simulation views from the contents of a user-specified file. This feature can be abused by an attacker to read arbitrary files from the Hoverfly server. Although the code prevents absolute paths from being specified, an attacker can escape out of the `hf.Cfg.ResponsesBodyFilesPath` base path by using `../` segments and reach any arbitrary files. This issue may lead to Information Disclosure. **Recommendations** As a temporary workaround, consider restricting access to the `/api/v2/simulation` endpoint until a patch is available. Make sure the final path (`filepath.Join(hf.Cfg.ResponsesBodyFilesPath, filePath)`) is contained within the expected base path (`filepath.Join(hf.Cfg.ResponsesBodyFilesPath, "/")`). 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** Kubernetes versions prior to 3385 **Description** The issue arises from the user-controlled `role` parameter entering the application in the Kubernetes::RoleVerificationsController. This parameter flows into the RoleConfigFile initializer and then into the Kubernetes::Util.parse file method, where it is unsafely deserialized using the YAML.load stream method. This may lead to Remote Code Execution (RCE). **Recommendations** For versions prior to 3385, update to version 3385 or later to resolve the issue. As a temporary workaround, consider restricting access to the Kubernetes::RoleVerificationsController to minimize the risk of exploitation. Avoid using the `role` parameter in the affected API endpoint until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Litestar versions 2.10.0 and prior **Description** The issue is related to Environment Variable injection in Litestar's `docs-preview.yml` workflow, which may lead to secret exfiltration and repository manipulation. This grants a malicious actor permission to write issues, read metadata, and write pull requests. The `DOCS PREVIEW DEPLOY TOKEN` is also exposed to the attacker. The vulnerability allows an attacker to send a malicious `.pr number` file, which can define new Environment Variables, including `LD PRELOAD`, to force the system to load a malicious shared library. This can result in arbitrary code execution when the `node` command is run. **Recommendations** For Litestar versions 2.10.0 and prior, verify the contents of the downloaded artifacts and do not allow new lines in the value redirected to `GITHUB ENV`. As a temporary workaround, consider restricting access to the `docs-preview.yml` workflow until a fix is applied. Update to a version that includes the fix, as commit 84d351e96aaa2a1338006d6e7221eded161f517b contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** JupyterLab extension template versions prior to 4.3.0 **Description** The JupyterLab extension template has a remote code execution (RCE) vulnerability in the `update-integration-tests.yml` workflow. This issue affects repositories created using the template with the `test` option. Extension authors are advised to upgrade the template to the latest version. Users who have modified the `update-integration-tests.yml` file should accept overwriting of this file and reapply their changes later. It is recommended to temporarily disable GitHub Actions while working on the upgrade and to rebase all open pull requests from untrusted users. **Recommendations** For versions prior to 4.3.0, upgrade the template to the latest version, overwriting the `update-integration-tests.yml` file if necessary, and reapply any changes made to this file later. As a temporary workaround, consider disabling GitHub Actions until the upgrade is complete. Restrict access to untrusted users' pull requests and rebase them to ensure actions run with the updated version.

**Name of the Vulnerable Software and Affected Versions** OpenMetadata versions prior to 1.3.1 **Description** The issue is related to incorrect code generation management in OpenMetadata, which can be exploited to execute arbitrary code remotely. An attacker can send a PUT request to "/api/v1/policies" to reach the vulnerable method. The `CompiledRule::validateExpression` function is called from `PolicyRepository.prepare`, and `prepare()` is called from `EntityRepository.prepareInternal()`, which in turn gets called from `EntityResource.createOrUpdate()`. Although there is an authorization check, it is called after the SpEL expression has been evaluated, allowing potential exploitation. This issue may lead to Remote Code Execution and has been addressed in version 1.3.1. **Recommendations** For OpenMetadata versions prior to 1.3.1, upgrade to version 1.3.1 to resolve the issue. As a temporary workaround, consider restricting access to the "/api/v1/policies" endpoint to minimize the risk of exploitation. Additionally, restricting the use of the `condition` parameter in the affected API endpoint can help mitigate the risk until a patch is applied.

**Name of the Vulnerable Software and Affected Versions** OpenMetadata versions prior to 1.2.4 **Description** The issue is related to the authentication mechanism in OpenMetadata, specifically with the `JwtFilter` that handles API authentication by verifying JWT tokens. An attacker can bypass the authentication mechanism by manipulating path parameters to make any path contain arbitrary strings, allowing access to arbitrary endpoints without JWT validation. This can lead to authentication bypass and potentially to arbitrary SpEL expression injection. The estimated number of potentially affected devices is not specified. **Recommendations** For versions prior to 1.2.4, upgrade to version 1.2.4 or later to address the authentication bypass issue. As a temporary workaround, consider restricting access to sensitive endpoints that may be vulnerable to SpEL expression injection until the upgrade is applied. Avoid using the `GET /api/v1;v1%2fusers%2flogin/events/subscriptions/validation/condition/111` endpoint or similar manipulated paths that can bypass JWT validation.

**Name of the Vulnerable Software and Affected Versions** OpenMetadata versions prior to 1.2.4 **Description** The issue is related to the `CompiledRule::validateExpression` method, which evaluates an SpEL expression using a `StandardEvaluationContext`. This allows the expression to interact with Java classes, such as `java.lang.Runtime`, leading to Remote Code Execution. The `/api/v1/policies/validation/condition/<expression>` endpoint passes user-controlled data to `CompiledRule::validateExpression`, enabling authenticated non-admin users to execute arbitrary system commands on the underlying operating system. A missing authorization check, as `Authorizer.authorize()` is never called in the affected path, allows any authenticated non-admin user to trigger this endpoint and evaluate arbitrary SpEL expressions, leading to arbitrary command execution. **Recommendations** For OpenMetadata versions prior to 1.2.4, upgrade to version 1.2.4 or later to resolve the issue. As a temporary workaround, consider restricting access to the `/api/v1/policies/validation/condition/<expression>` endpoint to prevent exploitation. Additionally, disabling the `CompiledRule::validateExpression` method or restricting the use of the `StandardEvaluationContext` until a patch is available can help minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** OpenMetadata versions prior to 1.2.4 **Description** The issue is related to the `AlertUtil::validateExpression` method, which can lead to Remote Code Execution. An attacker can send a PUT request to "/api/v1/events/subscriptions" to exploit this vulnerability. The `prepare()` method is called from `EntityRepository.prepareInternal()`, which in turn gets called from `EntityResource.createOrUpdate()`. Although there is an authorization check, it gets called after the SpEL expression has been evaluated. This vulnerability may lead to Remote Code Execution and has been addressed in version 1.2.4. **Recommendations** To resolve the issue, upgrade to version 1.2.4 or later. As a temporary workaround, consider disabling the `AlertUtil::validateExpression` function until a patch is available. Restrict access to the `/api/v1/events/subscriptions` API endpoint to minimize the risk of exploitation. Avoid using the `condition` parameter in the affected API endpoint until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** OpenMetadata versions prior to 1.2.4 **Description** The issue is related to the `AlertUtil::validateExpression` method, which evaluates an SpEL expression using `getValue` with the `StandardEvaluationContext`, allowing interaction with Java classes such as `java.lang.Runtime` and leading to Remote Code Execution. The `/api/v1/events/subscriptions/validation/condition/<expression>` endpoint passes user-controlled data to `AlertUtil::validateExpression`, enabling authenticated non-admin users to execute arbitrary system commands on the underlying operating system due to a missing authorization check. This may lead to Remote Code Execution. **Recommendations** For versions prior to 1.2.4, upgrade to version 1.2.4 or later to address the issue. As a temporary workaround, consider restricting access to the `/api/v1/events/subscriptions/validation/condition/<expression>` endpoint and disabling the `AlertUtil::validateExpression` method until a patch is available. Additionally, restrict the use of the `java.lang.Runtime` class to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Monkeytype versions prior to 24.30.0 **Description** The issue concerns a Poisoned Pipeline Execution through Code Injection in the ci-failure-comment.yml GitHub Workflow of Monkeytype. This vulnerability allows attackers to gain pull-requests write access by exploiting the lack of validation in the `steps.pr num reader.outputs.content` WorkFlow variable, which is later interpolated into a JS script. This enables an attacker to change the code to be executed. **Recommendations** For Monkeytype versions prior to 24.30.0, update to version 24.30.0 to fix the vulnerability. As a temporary workaround, consider restricting access to the ci-failure-comment.yml workflow to minimize the risk of exploitation. Avoid using the `steps.pr num reader.outputs.content` variable in the affected workflow until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Home assistant versions prior to 2023.9.0 **Description** The issue concerns a partial Server-Side Request Forgery vulnerability in the `hassio.addon stdin` service, where an attacker capable of calling this service may be able to invoke any Supervisor REST API endpoints with a POST request. This could allow the attacker to control the data dictionary, including its addon and input key/values. **Recommendations** For versions prior to 2023.9.0, upgrade to version 2023.9.0 or later to address the issue. As a temporary workaround, consider restricting access to the `hassio.addon stdin` service until the upgrade is possible. Additionally, be cautious when using Supervisor REST API endpoints to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Home Assistant Companion for iOS and macOS versions up to 2023.4 **Description** The issue allows attackers to send malicious links or QRs to victims, which can lead to calling arbitrary services in their Home Assistant installation. This can result in full compromise and remote code execution (RCE) when combined with other security advisories. **Recommendations** For versions up to 2023.4, upgrade to version 2023.7 to address this issue. At the moment, there is no information about other workarounds for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Jenkins Bitbucket Push and Pull Request Plugin versions 2.4.0 through 2.8.3 **Description** The issue allows attackers to capture Bitbucket credentials stored in Jenkins by sending a crafted webhook payload. This is possible because the plugin trusts values provided in the webhook payload, including certain URLs, and uses configured Bitbucket credentials to connect to those URLs. **Recommendations** For Jenkins Bitbucket Push and Pull Request Plugin versions 2.4.0 through 2.8.3, update to a version that fixes the issue, as the current versions trust values provided in the webhook payload, allowing potential exploitation. 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 Blue Ocean Plugin versions 1.27.5 and earlier **Description** A cross-site request forgery (CSRF) vulnerability allows attackers to connect to an attacker-specified URL, capturing GitHub credentials associated with an attacker-specified job. This issue is due to an incomplete fix and results from not requiring POST requests for an HTTP endpoint. The vulnerability enables attackers to exploit the `HTTP endpoint` and capture sensitive information. **Recommendations** For Jenkins Blue Ocean Plugin versions 1.27.5 and earlier, update to a version that includes the complete fix for the issue, such as version 1.27.5.1, which uses the configured SCM URL instead of a user-specified URL. As a temporary workaround, consider restricting access to the vulnerable HTTP endpoint until a patch is applied.

**Name of the Vulnerable Software and Affected Versions** Jenkins Maven Artifact ChoiceListProvider (Nexus) Plugin versions 1.14 and earlier **Description** The issue is related to insufficient protection of registration data, allowing attackers with Item/Configure permission to access and capture credentials they are not entitled to. This is due to the plugin not setting the appropriate context for credentials lookup. Attackers can exploit this to gain unauthorized access to protected information. **Recommendations** For Jenkins Maven Artifact ChoiceListProvider (Nexus) Plugin versions 1.14 and earlier, as a temporary workaround, consider restricting access to the plugin until a patch is available. Additionally, limit the use of System-scoped credentials to minimize the risk of exploitation. 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 GitLab Authentication Plugin versions 1.17.1 and earlier **Description** A cross-site request forgery (CSRF) vulnerability allows attackers to trick users into logging in to the attacker's account. This issue arises because the plugin does not implement a state parameter in its OAuth flow, which is a unique and non-guessable value associated with each authentication request. **Recommendations** For Jenkins GitLab Authentication Plugin versions 1.17.1 and earlier, update to version 1.18 or later, which implements a state parameter in its OAuth flow.

**Name of the Vulnerable Software and Affected Versions** Jenkins mabl Plugin versions 0.0.46 and earlier **Description** A missing permission check in the Jenkins mabl Plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. The plugin does not perform permission checks in several HTTP endpoints, which also results in a cross-site request forgery (CSRF) vulnerability due to not requiring POST requests. **Recommendations** For Jenkins mabl Plugin versions 0.0.46 and earlier, update to version 0.0.47 or later, which requires POST requests and the appropriate permissions for the affected HTTP endpoints. As a temporary workaround, consider restricting access to the affected HTTP endpoints to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Jenkins Datadog Plugin versions 5.4.1 and earlier **Description** A missing permission check in the Jenkins Datadog Plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs, capturing credentials stored in Jenkins. The issue is related to an HTTP endpoint that does not perform a permission check, enabling attackers to exploit this vulnerability. **Recommendations** For Jenkins Datadog Plugin versions 5.4.1 and earlier, update to version 5.4.2 or later, which requires Overall/Administer permission to access the affected HTTP endpoint, thereby mitigating the risk of exploitation.