Summary
fish-shop/syntax-check Improper Neutralization of Delimiters
Workarounds
Is it recommended that users update to the patched version v1.6.12 or the latest release version v2.0.0, however remediation may be possible through careful control of workflows and the pattern input value used by this action.
References
Impact
Improper neutralisation of delimiters in the pattern input (specifically the command separator ; and command substitution characters ( and )) mean that arbitrary command injection is possible by modification of the input value used in a workflow. This has the potential for exposure or exfiltration of sensitive information from the workflow runner, such as might be achieved by sending environment variables to an external entity.
CVE-2024-42482 has a CVSS score of 4.8 (Medium). 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 (1.6.12); upgrading removes the vulnerable code path.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
As of this writing, the issue has been patched for versions in the v1.x.x release series in release v1.6.12 (also tagged as v1.6 and v1). The latest available release v2.0.0 also includes a corresponding patch (also tagged as v2.0 and v2).
Users should upgrade to at least the patched version v1.6.12 or preferably the latest available version v2.0.0. Workflows that use the action ref v1 will automatically receive the patched version v1.6.12 in future workflow runs.
Patch summary:
| Release series | Patched tags | Patched commit hashes |
|---|---|---|
1.x.x |
v1.6.12, v1.6, v1 |
91e6817c48ad475542fe4e78139029b036a53b03 |
2.x.x |
v2.0.0, v2.0, v2 |
c2cb11395e21119ff8d6e7ea050430ee7d6f49ca |
Frequently Asked Questions
- What is CVE-2024-42482? CVE-2024-42482 is a medium-severity security vulnerability in fish-shop/syntax-check (actions), affecting versions < 1.6.12. It is fixed in 1.6.12.
- How severe is CVE-2024-42482? CVE-2024-42482 has a CVSS score of 4.8 (Medium). 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 fish-shop/syntax-check are affected by CVE-2024-42482? fish-shop/syntax-check (actions) versions < 1.6.12 is affected.
- Is there a fix for CVE-2024-42482? Yes. CVE-2024-42482 is fixed in 1.6.12. Upgrade to this version or later.
- Is CVE-2024-42482 exploitable, and should I be worried? Whether CVE-2024-42482 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-42482 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-42482? Upgrade
fish-shop/syntax-checkto 1.6.12 or later.