VulnerabilityPublished 10 Apr 2024Updated 4 Nov 2025

CVE-2024-2243: csmock · OS Command Injection

Affects csmockSource CVE Database V5

Not known to be exploited · CVSS 7.6 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hatredhat/csmock`pkg:rpm/redhat/csmock`Other threats	Affected =3.5.1 =3.5.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-2243, organizations should immediately upgrade csmock to a version where this vulnerability is patched once available. In the absence of an official patch, restrict access to OSH services to only trusted users and enforce strict Kerberos ticket issuance policies to limit potential attackers. Implement network segmentation to isolate OSH worker nodes from sensitive infrastructure and monitor command execution logs for suspicious activity indicative of injection attempts. Employ runtime security tools that can detect and block anomalous OS command executions within containerized environments. Additionally, rotate and revoke Snyk authentication tokens to prevent misuse if token disclosure has occurred. Conduct thorough code reviews and input validation audits in custom integrations with OSH or similar services to prevent injection flaws. Finally, consider deploying multi-factor authentication for Kerberos ticket acquisition to reduce the risk of credential compromise and unauthorized access.

Description

A vulnerability was found in csmock where a regular user of the OSH service (anyone with a valid Kerberos ticket) can use the vulnerability to disclose the confidential Snyk authentication token and to run arbitrary commands on OSH workers.

Impact

The impact of CVE-2024-2243 is significant for organizations using csmock versions 3.5.1 or 3.5.2 in conjunction with OSH services. An attacker with a valid Kerberos ticket can execute arbitrary commands on OSH worker nodes, potentially leading to unauthorized access, data exfiltration, and disruption of hosted services. The disclosure of the confidential Snyk authentication token further exacerbates the risk by enabling attackers to manipulate or bypass security scanning processes, possibly allowing malicious code to go undetected. This can compromise the integrity of software supply chains and increase the risk of persistent threats. The vulnerability affects confidentiality primarily, with some impact on availability and integrity due to the arbitrary command execution capability. Organizations relying on Kerberos for authentication and deploying OSH workers in production environments face elevated risk, particularly if they have not updated csmock or implemented compensating controls. The ease of exploitation and the potential for lateral movement within the network make this a critical concern for cloud-native infrastructure security and container orchestration environments.

References

Community reviews

Loading reviews…