What is CVE-2024-42360?

CVE-2024-42360 is a critical-severity command injection vulnerability in sequenceserver (rubygems), affecting versions < 3.1.2. It is fixed in 3.1.2. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.

How severe is CVE-2024-42360?

CVE-2024-42360 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of sequenceserver are affected by CVE-2024-42360?

sequenceserver (rubygems) versions < 3.1.2 is affected.

Is there a fix for CVE-2024-42360?

Yes. CVE-2024-42360 is fixed in 3.1.2. Upgrade to this version or later.

Is CVE-2024-42360 exploitable, and should I be worried?

Whether CVE-2024-42360 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-42360 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-42360 in sequenceserver

Q: How severe is CVE-2024-42360?

CVE-2024-42360 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of sequenceserver are affected by CVE-2024-42360?

sequenceserver (rubygems) versions < 3.1.2 is affected.

Q: Is there a fix for CVE-2024-42360?

Yes. CVE-2024-42360 is fixed in 3.1.2. Upgrade to this version or later.

Q: Is CVE-2024-42360 exploitable, and should I be worried?

Whether CVE-2024-42360 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-42360 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-42360?

Upgrade sequenceserver to 3.1.2 or later.

Summary

Command Injection in sequenceserver

Fixed in 3.1.2

Workarounds

No known workarounds

Impact

Several HTTP endpoints did not properly sanitize user input and/or query parameters. This could be exploited to inject and run unwanted shell commands

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2024-42360 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.2); upgrading removes the vulnerable code path.

Affected versions

sequenceserver (< 3.1.2)

Security releases

sequenceserver → 3.1.2 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade sequenceserver to 3.1.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-42360? CVE-2024-42360 is a critical-severity command injection vulnerability in sequenceserver (rubygems), affecting versions < 3.1.2. It is fixed in 3.1.2. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
How severe is CVE-2024-42360? CVE-2024-42360 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of sequenceserver are affected by CVE-2024-42360? sequenceserver (rubygems) versions < 3.1.2 is affected.
Is there a fix for CVE-2024-42360? Yes. CVE-2024-42360 is fixed in 3.1.2. Upgrade to this version or later.
Is CVE-2024-42360 exploitable, and should I be worried? Whether CVE-2024-42360 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-42360 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-42360? Upgrade sequenceserver to 3.1.2 or later.