GHSA-xrv8-2pf5-f3q7: Nitro tpm pcr compute Nitro-tpm-pcr-compute May Allow Kernel Command Vulnerability

MODERATE
CVSS 6.0
CWE-77
Published
Advisory Summary

GHSA-xrv8-2pf5-f3q7 is a MODERATE (CVSS 6.0) nitro-tpm-pcr-compute may allow kernel command vulnerability (CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')) affecting Nitro tpm pcr compute libraries in the crates.io ecosystem. The issue involves nitro-tpm-pcr-compute may allow kernel command line modification by an account operator. Remediation is available by upgrading affected packages to version 1.1.0.

GHSA-xrv8-2pf5-f3q7 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-xrv8-2pf5-f3q7
Severity MODERATE
CVSS v3.1 Base Score 6.0
CWE Classification CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Affected Product Nitro tpm pcr compute
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 6.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix GHSA-xrv8-2pf5-f3q7

To remediate this vulnerability, upgrade all affected Nitro tpm pcr compute dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nitro-tpm-pcr-compute fixed: 1.1.0
Upgrade nitro-tpm-pcr-compute to 1.1.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for nitro-tpm-pcr-compute

How to Check if You Are Affected

To determine whether your application is affected by GHSA-xrv8-2pf5-f3q7, inspect your project dependencies for Nitro tpm pcr compute:

inspect dependencies for nitro-tpm-pcr-compute

Analyze the terminal output to locate any version of Nitro tpm pcr compute in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.1.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'), where the product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. In Nitro tpm pcr compute, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Adding default PCR12 validation to ensure that account operators can not modify kernel command line parameters, potentially bypassing root filesystem integrity validation. Attestable AMIs are based on the systemd Unified Kernel Image (UKI) concept which uses systemd-boot to create a single measured UEFI binary from a Linux kernel, its initramfs, and kernel command line. The embedded kernel command line contains a dm-verity hash value that establishes trust in the root file system. When UEFI Secure Boot is disabled, systemd-boot appends any command line it receives to the kernel command line. Account operators with the ability to modify UefiData can install a boot variable with a command line that deactivates root file system integrity validation, while preserving the original PCR4 value. Systemd-boot provides separate measurement of command line modifications in PCR12. ## Impact 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. ## Patches 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: ```json { "Measurements": { "HashAlgorithm": "SHA384", "PCR4": "<hex string>", "PCR7": "<hex string>", "PCR12": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" } } ``` ## Workarounds For users who cannot upgrade to version 1.1.0 of nitro-tpm-pcr-compute immediately, the following workarounds are available: 1. **Manually add PCR12 to KMS policies:** Add PCR12 with a static zero value to your AWS KMS key policies: ```txt kms:RecipientAttestation:NitroTPMPCR12:000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ``` 2. **Enable and validate UEFI Secure Boot:** Configure your Attestable AMI to use UEFI Secure Boot and validate its enablement via PCR7 in your KMS policy. When UEFI Secure Boot is active, the command line cannot be overwritten.

GHSA-xrv8-2pf5-f3q7 Affected Nitro tpm pcr compute Versions

1 component(s)
Fixed Versions:
1.1.0
Product / Package Ecosystem Affected Versions Fixed Version
nitro-tpm-pcr-compute
crates.io
< 1.1.0
1.1.0

References

Frequently Asked Questions

What is GHSA-xrv8-2pf5-f3q7?
GHSA-xrv8-2pf5-f3q7 is a security vulnerability in Nitro tpm pcr compute involving nitro-tpm-pcr-compute may allow kernel command line modification by an account operator under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection').
Which Nitro tpm pcr compute versions are affected?
Affected versions include releases prior to 1.1.0 across affected packages: nitro-tpm-pcr-compute.
What version fixes GHSA-xrv8-2pf5-f3q7?
Upgrading to 1.1.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nitro-tpm-pcr-compute affected?
Yes, nitro-tpm-pcr-compute is affected in releases prior to 1.1.0. Upgrade your dependency to 1.1.0 or later.
What is the CVSS score of GHSA-xrv8-2pf5-f3q7?
GHSA-xrv8-2pf5-f3q7 has a CVSS v3.1 base score of 6.0 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with GHSA-xrv8-2pf5-f3q7?
GHSA-xrv8-2pf5-f3q7 is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') (The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.).
How can I check crates.io dependencies for GHSA-xrv8-2pf5-f3q7?
Run the dependency tree command: 'inspect dependencies for nitro-tpm-pcr-compute'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xrv8-2pf5-f3q7",
  "modified" : "2025-12-05T18:57:55Z",
  "published" : "2025-12-05T18:57:55Z",
  "aliases" : [ ],
  "summary" : "nitro-tpm-pcr-compute may allow kernel command line modification by an account operator",
  "details" : "## Summary\n\nAdding default PCR12 validation to ensure that account operators can not modify kernel command line parameters, potentially bypassing root filesystem integrity validation.\n\nAttestable AMIs are based on the systemd Unified Kernel Image (UKI) concept which uses systemd-boot to create a single measured UEFI binary from a Linux kernel, its initramfs, and kernel command line. The embedded kernel command line contains a dm-verity hash value that establishes trust in the root file system.\n\nWhen UEFI Secure Boot is disabled, systemd-boot appends any command line it receives to the kernel command line. Account operators with the ability to modify UefiData can install a boot variable with a command line that deactivates root file system integrity validation, while preserving the original PCR4 value.\n\nSystemd-boot provides separate measurement of command line modifications in PCR12.\n\n## Impact\n\nIn 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.\n\n## Patches \n\nVersion 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:\n\n```json\n{\n  \"Measurements\": {\n    \"HashAlgorithm\": \"SHA384\",\n    \"PCR4\": \"<hex string>\",\n    \"PCR7\": \"<hex string>\",\n    \"PCR12\": \"000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000\"\n  }\n}\n```\n\n## Workarounds\n\nFor users who cannot upgrade to version 1.1.0 of nitro-tpm-pcr-compute immediately, the following workarounds are available:\n\n1. **Manually add PCR12 to KMS policies:** Add PCR12 with a static zero value to your AWS KMS key policies:\n\n```txt\nkms:RecipientAttestation:NitroTPMPCR12:000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000\n```\n\n2. **Enable and validate UEFI Secure Boot:** Configure your Attestable AMI to use UEFI Secure Boot and validate its enablement via PCR7 in your KMS policy. When UEFI Secure Boot is active, the command line cannot be overwritten.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "nitro-tpm-pcr-compute"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.1.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/aws/nitrotpm-attestation-samples/security/advisories/GHSA-xrv8-2pf5-f3q7"
  }, {
    "type" : "WEB",
    "url" : "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/attestable-ami.html"
  }, {
    "type" : "WEB",
    "url" : "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/uefi-secure-boot.html"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aws/NitroTPM-Tools"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aws/NitroTPM-Tools/blob/main/CHANGELOG.md"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aws/NitroTPM-Tools/releases/tag/v1.1.0"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/aws/nitrotpm-attestation-samples"
  }, {
    "type" : "WEB",
    "url" : "https://www.freedesktop.org/software/systemd/man/latest/systemd-stub.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-77" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-05T18:57:55Z",
    "nvd_published_at" : null
  }
}