What is GHSA-XCPM-76HF-C9CC?

GHSA-XCPM-76HF-C9CC is a low-severity security vulnerability in borrowck_sacrifices (rust), affecting versions < 0.2.0. It is fixed in 0.2.0.

Which versions of borrowck_sacrifices are affected by GHSA-XCPM-76HF-C9CC?

borrowck_sacrifices (rust) versions < 0.2.0 is affected.

Is there a fix for GHSA-XCPM-76HF-C9CC?

Yes. GHSA-XCPM-76HF-C9CC is fixed in 0.2.0. Upgrade to this version or later.

Is GHSA-XCPM-76HF-C9CC exploitable, and should I be worried?

Whether GHSA-XCPM-76HF-C9CC 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 GHSA-XCPM-76HF-C9CC 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.

GHSA-XCPM-76HF-C9CC in borrowck_sacrifices

Q: Which versions of borrowck_sacrifices are affected by GHSA-XCPM-76HF-C9CC?

borrowck_sacrifices (rust) versions < 0.2.0 is affected.

Q: Is there a fix for GHSA-XCPM-76HF-C9CC?

Yes. GHSA-XCPM-76HF-C9CC is fixed in 0.2.0. Upgrade to this version or later.

Q: Is GHSA-XCPM-76HF-C9CC exploitable, and should I be worried?

Whether GHSA-XCPM-76HF-C9CC 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 GHSA-XCPM-76HF-C9CC 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 GHSA-XCPM-76HF-C9CC?

Upgrade borrowck_sacrifices to 0.2.0 or later.

Summary

Borrowck Scarifices exposes uninitialized memory in anyasu8_slice

The safe function any_as_u8_slice can create byte slices that reference uninitialized memory when used with types containing padding bytes.

The function uses slice::from_raw_parts to create a &[u8] covering the entire size of a type, including padding bytes. According to Rust's documentation, from_raw_parts requires all bytes to be properly initialized, but padding bytes in structs are not guaranteed to be initialized. This violates the safety contract and causes undefined behavior.

Impact

Affected versions

borrowck_sacrifices (< 0.2.0)

Security releases

borrowck_sacrifices → 0.2.0 (rust)

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 borrowck_sacrifices to 0.2.0 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 GHSA-XCPM-76HF-C9CC? GHSA-XCPM-76HF-C9CC is a low-severity security vulnerability in borrowck_sacrifices (rust), affecting versions < 0.2.0. It is fixed in 0.2.0.
Which versions of borrowck_sacrifices are affected by GHSA-XCPM-76HF-C9CC? borrowck_sacrifices (rust) versions < 0.2.0 is affected.
Is there a fix for GHSA-XCPM-76HF-C9CC? Yes. GHSA-XCPM-76HF-C9CC is fixed in 0.2.0. Upgrade to this version or later.
Is GHSA-XCPM-76HF-C9CC exploitable, and should I be worried? Whether GHSA-XCPM-76HF-C9CC 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 GHSA-XCPM-76HF-C9CC 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 GHSA-XCPM-76HF-C9CC? Upgrade borrowck_sacrifices to 0.2.0 or later.