GHSA-XRV8-2PF5-F3Q7

nitro-tpm-pcr-compute may allow kernel command line modification by an account operator

In line with the TPM 2.0 specification and systemd-stub logic, KMS policies that do not include validation for PCR12 (command line measurement) or PCR7 (enabled Secure Boot) may allow kernel command line modification by an account operator.

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.

GHSA-XRV8-2PF5-F3Q7 has a CVSS score of 6.0 (Medium). The vector is requires local access, high 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.1.0); upgrading removes the vulnerable code path.

Kodem intelligence

Version 1.1.0 of nitro-tpm-pcr-compute has been updated to include PCR12 with a static zero value. The updated tool now outputs PCR12 in the JSON measurements:

{
  "Measurements": {
    "HashAlgorithm": "SHA384",
    "PCR4": "<hex string>",
    "PCR7": "<hex string>",
    "PCR12": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
  }
}

1. What is GHSA-XRV8-2PF5-F3Q7? GHSA-XRV8-2PF5-F3Q7 is a medium-severity command injection vulnerability in nitro-tpm-pcr-compute (rust), affecting versions < 1.1.0. It is fixed in 1.1.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
2. How severe is GHSA-XRV8-2PF5-F3Q7? GHSA-XRV8-2PF5-F3Q7 has a CVSS score of 6.0 (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.
3. Which versions of nitro-tpm-pcr-compute are affected by GHSA-XRV8-2PF5-F3Q7? nitro-tpm-pcr-compute (rust) versions < 1.1.0 is affected.
4. Is there a fix for GHSA-XRV8-2PF5-F3Q7? Yes. GHSA-XRV8-2PF5-F3Q7 is fixed in 1.1.0. Upgrade to this version or later.
5. Is GHSA-XRV8-2PF5-F3Q7 exploitable, and should I be worried? Whether GHSA-XRV8-2PF5-F3Q7 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 GHSA-XRV8-2PF5-F3Q7 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 GHSA-XRV8-2PF5-F3Q7? Upgrade nitro-tpm-pcr-compute to 1.1.0 or later.