{"answers":{"affected":"2 open source packages ship an affected version, including nitro-tpm-pcr-compute.","exploited":"There is no known exploitation of GHSA-xrv8-2pf5-f3q7 in the wild and no public exploit code.","fix":"Upgrade nitro-tpm-pcr-compute to 1.1.0 or later.","what":"GHSA-xrv8-2pf5-f3q7 is a vulnerability in nitro-tpm-pcr-compute, published on 5 Dec 2025."},"fix_prompt":"Check this codebase for GHSA-xrv8-2pf5-f3q7 and fix it if it is affected.\n\nWhat it is: GHSA-xrv8-2pf5-f3q7 is a vulnerability in nitro-tpm-pcr-compute, published on 5 Dec 2025. \nExploitation: There is no known exploitation of GHSA-xrv8-2pf5-f3q7 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nitro-tpm-pcr-compute (crates.io): affected all versions; fixed in 1.1.0\n- nitro-tpm-pcr-compute (crates.io): affected all versions; fixed in 1.1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-xrv8-2pf5-f3q7/ (Markdown: https://insights.sbomify.com/GHSA-xrv8-2pf5-f3q7/index.md)","id":"GHSA-xrv8-2pf5-f3q7","markdown":"https://insights.sbomify.com/GHSA-xrv8-2pf5-f3q7/index.md","name":"GHSA-xrv8-2pf5-f3q7","record":{"aliases":[],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"unknown","non_default_config":true,"product_category":"AWS Nitro TPM tool","requires_auth":"low_privilege","summary":"Account operators can bypass root filesystem integrity validation by modifying kernel command lines if PCR12 is not validated in KMS policies.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"## 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\": \"\u003chex string\u003e\",\n    \"PCR7\": \"\u003chex string\u003e\",\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.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"nitro-tpm-pcr-compute may allow kernel command line modification by an account operator","id":"GHSA-xrv8-2pf5-f3q7","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"nitro-tpm-pcr-compute","purl":null,"source":"GHSA-xrv8-2pf5-f3q7"},{"ecosystem":"crates.io","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"nitro-tpm-pcr-compute","purl":"pkg:cargo/nitro-tpm-pcr-compute","source":"GHSA-xrv8-2pf5-f3q7"}],"products":null,"published":"2025-12-05","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Account operators can bypass root filesystem integrity validation by modifying kernel command lines if PCR12 is not validated in KMS policies.","url":"https://insights.sbomify.com/GHSA-xrv8-2pf5-f3q7/"}