CVE-2024-41956

Workarounds

None.

References

n/a.

It is possible for a user who can commit files to a repository hosted by Soft Serve to execute arbitrary code via environment manipulation and Git.

The issue is that Soft Serve passes all environment variables given by the client to git subprocesses. This includes environment variables that control program execution, such as LD_PRELOAD.

This can be exploited to execute arbitrary code by, for example, uploading a malicious shared object file to Soft Serve via Git LFS (uploading it via LFS ensures that it is not compressed on disk and easier to work with). The file will be stored under its SHA256 hash, so it has a predictable name.

This file can then be referenced in LD_PRELOAD via a Soft Serve SSH session that causes git to be invoked. For example:

LD_PRELOAD=/.../data/lfs/1/objects/a2/b5/a2b585befededf5f95363d06d83655229e393b1b45f76d9f989a336668665a2f ssh server git-upload-pack repo

The example LFS file patches a shared library function called by git to execute a shell.

Any servers using soft-serve server and git

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2024-41956 has a CVSS score of 8.1 (High). The vector is network-reachable, low 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 (0.7.5); upgrading removes the vulnerable code path.

Kodem intelligence

0.7.5

1. What is CVE-2024-41956? CVE-2024-41956 is a high-severity OS command injection vulnerability in github.com/charmbracelet/soft-serve (go), affecting versions < 0.7.5. It is fixed in 0.7.5. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2024-41956? CVE-2024-41956 has a CVSS score of 8.1 (High). 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.
3. Which versions of github.com/charmbracelet/soft-serve are affected by CVE-2024-41956? github.com/charmbracelet/soft-serve (go) versions < 0.7.5 is affected.
4. Is there a fix for CVE-2024-41956? Yes. CVE-2024-41956 is fixed in 0.7.5. Upgrade to this version or later.
5. Is CVE-2024-41956 exploitable, and should I be worried? Whether CVE-2024-41956 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
6. What actually determines whether CVE-2024-41956 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.
7. How do I fix CVE-2024-41956? Upgrade github.com/charmbracelet/soft-serve to 0.7.5 or later.