What is CVE-2024-24579?

CVE-2024-24579 is a medium-severity path traversal vulnerability in github.com/anchore/stereoscope (go), affecting versions < 0.0.1. It is fixed in 0.0.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

How severe is CVE-2024-24579?

CVE-2024-24579 has a CVSS score of 5.3 (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 github.com/anchore/stereoscope are affected by CVE-2024-24579?

github.com/anchore/stereoscope (go) versions < 0.0.1 is affected.

Is there a fix for CVE-2024-24579?

Yes. CVE-2024-24579 is fixed in 0.0.1. Upgrade to this version or later.

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

Whether CVE-2024-24579 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-24579 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-24579?

Upgrade github.com/anchore/stereoscope to 0.0.1 or later.

CVE-2024-24579 in github.com/anchore/stereoscope

Q: How severe is CVE-2024-24579?

CVE-2024-24579 has a CVSS score of 5.3 (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.

Q: Which versions of github.com/anchore/stereoscope are affected by CVE-2024-24579?

github.com/anchore/stereoscope (go) versions < 0.0.1 is affected.

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

Yes. CVE-2024-24579 is fixed in 0.0.1. Upgrade to this version or later.

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

Whether CVE-2024-24579 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-24579 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-24579?

Upgrade github.com/anchore/stereoscope to 0.0.1 or later.

Summary

stereoscope vulnerable to tar path traversal when processing OCI tar archives

Workarounds

If you are using the OCI archive as input into stereoscope then you can switch to using an OCI layout by unarchiving the tar archive and provide the unarchived directory to stereoscope.

References

Patch PR https://github.com/anchore/stereoscope/pull/214

Impact

It is possible to craft an OCI tar archive that, when stereoscope attempts to unarchive the contents, will result in writing to paths outside of the unarchive temporary directory. Specifically, use of github.com/anchore/stereoscope/pkg/file.UntarToDirectory() function, the github.com/anchore/stereoscope/pkg/image/oci.TarballImageProvider struct, or the higher level github.com/anchore/stereoscope/pkg/image.Image.Read() function express this vulnerability.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2024-24579 has a CVSS score of 5.3 (Medium). The vector is requires local access, no privileges required, and user interaction required. 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.0.1); upgrading removes the vulnerable code path.

Affected versions

github.com/anchore/stereoscope (< 0.0.1)

Security releases

github.com/anchore/stereoscope → 0.0.1 (go)

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

Patched in v0.0.1

Frequently Asked Questions

What is CVE-2024-24579? CVE-2024-24579 is a medium-severity path traversal vulnerability in github.com/anchore/stereoscope (go), affecting versions < 0.0.1. It is fixed in 0.0.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
How severe is CVE-2024-24579? CVE-2024-24579 has a CVSS score of 5.3 (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 github.com/anchore/stereoscope are affected by CVE-2024-24579? github.com/anchore/stereoscope (go) versions < 0.0.1 is affected.
Is there a fix for CVE-2024-24579? Yes. CVE-2024-24579 is fixed in 0.0.1. Upgrade to this version or later.
Is CVE-2024-24579 exploitable, and should I be worried? Whether CVE-2024-24579 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-24579 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-24579? Upgrade github.com/anchore/stereoscope to 0.0.1 or later.