embano1 wip 1.x Run github.event.pull_request.title command injection

Summaryinfo

A vulnerability was found in embano1 wip 1.x. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component Run Handler. Performing a manipulation of the argument github.event.pull_request.title results in command injection. This vulnerability is reported as CVE-2023-30623. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in embano1 wip 1.x. It has been classified as critical. This affects an unknown code block of the component Run Handler. The manipulation of the argument github.event.pull_request.title with an unknown input leads to a command injection vulnerability. CWE is classifying the issue as CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

`embano1/wip` is a GitHub Action written in Bash. Prior to version 2, the `embano1/wip` action uses the `github.event.pull_request.title` parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation. This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). The commit can be genuine, but the commit message can be malicious. This can be used to execute code on the GitHub runners and can be used to exfiltrate any secrets used in the CI pipeline, including repository tokens. Version 2 has a fix for this issue.

The weakness was disclosed 04/25/2023 as GHSA-rg3q-prf8-qxmp. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-30623 since 04/13/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1202 for this issue.

Upgrading to version 2 eliminates this vulnerability. Applying the patch c25450f77ed02c20d00b76ee3b33ff43838739a2 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• embano1

Name

• wip

Version

• 1.x

License

• open-source

Website

• Product: https://github.com/embano1/wip/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion