mehah OTCLient SonarCloud Workflow /mehah/otclient injection

Summaryinfo

A vulnerability, which was classified as very critical, has been found in mehah OTCLient. This affects an unknown part of the file /mehah/otclient of the component SonarCloud Workflow. Performing a manipulation results in injection. This vulnerability is reported as CVE-2024-21623. The attack is possible to be carried out remotely. No exploit exists. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability, which was classified as very critical, was found in mehah OTCLient (affected version unknown). This affects an unknown functionality of the file /mehah/otclient of the component SonarCloud Workflow. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted 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:

OTCLient is an alternative tibia client for otserv. Prior to commit db560de0b56476c87a2f967466407939196dd254, the /mehah/otclient "`Analysis - SonarCloud`" workflow is vulnerable to an expression injection in Actions, allowing an attacker to run commands remotely on the runner, leak secrets, and alter the repository using this workflow. Commit db560de0b56476c87a2f967466407939196dd254 contains a fix for this issue.

The weakness was disclosed 01/03/2024 as GHSA-q6gr-wc79-v589. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-21623 since 12/29/2023. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/03/2024). MITRE ATT&CK project uses the attack technique T1055 for this issue.

Applying the patch db560de0b56476c87a2f967466407939196dd254 is able to eliminate this problem. The bugfix is ready for download at github.com.

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

Productinfo

Vendor

• mehah

Name

• OTCLient

License

• open-source

Website

• Product: https://github.com/mehah/otclient/

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