# CVE-2022-0317: Improper Input Validation in AKPublic.Verify in go-attestation

> A local attacker can bypass measured boot attestation by spoofing TCG log events due to improper input validation in go-attestation.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2022
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-99cg-575x-774p, GO-2022-0294

## What is CVE-2022-0317?

CVE-2022-0317 is a medium-severity vulnerability in Google LLC go-attestation, published on 4 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An improper input validation vulnerability in go-attestation before 0.3.3 allows local users to provide a maliciously-formed Quote over no/some PCRs, causing AKPublic.Verify to succeed despite the inconsistency. Subsequent use of the same set of PCR values in Eventlog.Verify lacks the authentication performed by quote verification, meaning a local attacker could couple this vulnerability with a maliciously-crafted TCG log in Eventlog.Verify to spoof events in the TCG log, hence defeating remotely-attested measured-boot. We recommend upgrading to Version 0.4.0 or above.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-0317?

3 open source packages ship an affected version, including github.com/google/go-attestation. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/google/go-attestation` | Go | All versions | 0.4.0 |
| `github.com/google/go-attestation` | Go | All versions | 0.4.0 |
| `github.com/google/go-attestation` | Go | All versions | 0.4.0 |

Products: Google Go-Attestation.

## How do I fix CVE-2022-0317?

Upgrade github.com/google/go-attestation to 0.4.0 or later.

## Is CVE-2022-0317 being exploited?

There is no known exploitation of CVE-2022-0317 in the wild and no public exploit code.

## Other vulnerabilities in Google LLC go-attestation

- [CVE-2026-19201](https://insights.sbomify.com/CVE-2026-19201/): Denial of Service via Unbounded Recursion in go-attestation Windows SIPA Parser (medium 6.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0317 and fix it if it is affected.

What it is: CVE-2022-0317 is a medium-severity vulnerability in Google LLC go-attestation, published on 4 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0317 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/google/go-attestation (Go): affected all versions; fixed in 0.4.0
- github.com/google/go-attestation (Go): affected all versions; fixed in 0.4.0
- github.com/google/go-attestation (Go): affected all versions; fixed in 0.4.0

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0317/ (Markdown: https://insights.sbomify.com/CVE-2022-0317/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0317
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0317
- OSV: https://osv.dev/vulnerability/CVE-2022-0317

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0317/
Summaries are generated and may contain mistakes; the official description above is the record.