What is CVE-2022-0317?

CVE-2022-0317 is a medium-severity improper input validation vulnerability in github.com/google/go-attestation (go), affecting versions < 0.4.0. It is fixed in 0.4.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2022-0317?

CVE-2022-0317 has a CVSS score of 4.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.

Which versions of github.com/google/go-attestation are affected by CVE-2022-0317?

github.com/google/go-attestation (go) versions < 0.4.0 is affected.

Is there a fix for CVE-2022-0317?

Yes. CVE-2022-0317 is fixed in 0.4.0. Upgrade to this version or later.

Is CVE-2022-0317 exploitable, and should I be worried?

Whether CVE-2022-0317 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 CVE-2022-0317 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 CVE-2022-0317?

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

CVE-2022-0317 in github.com/google/go-attestation | Intelligent Application Security

Q: How severe is CVE-2022-0317?

CVE-2022-0317 has a CVSS score of 4.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.

Q: Which versions of github.com/google/go-attestation are affected by CVE-2022-0317?

github.com/google/go-attestation (go) versions < 0.4.0 is affected.

Q: Is there a fix for CVE-2022-0317?

Yes. CVE-2022-0317 is fixed in 0.4.0. Upgrade to this version or later.

Q: Is CVE-2022-0317 exploitable, and should I be worried?

Whether CVE-2022-0317 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 CVE-2022-0317 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 CVE-2022-0317?

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

Summary

Go-Attestation Improper Input Validation with attacker-controlled TPM Quote

Impact

An improper input validation vulnerability in go-attestation before 0.4.0 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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2022-0317 has a CVSS score of 4.0 (Medium). The vector is requires local access, no 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 (0.4.0); upgrading removes the vulnerable code path.

Affected versions

github.com/google/go-attestation (< 0.4.0)

Security releases

github.com/google/go-attestation → 0.4.0 (go)

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.

See it in your environment

Remediation advice

This issue is resolved in version 0.4.0. If your usage of this library verifies PCRs using multiple quotes, make sure to use the new method AKPublic.VerifyAll() instead of AKPublic.Verify.

Frequently Asked Questions

What is CVE-2022-0317? CVE-2022-0317 is a medium-severity improper input validation vulnerability in github.com/google/go-attestation (go), affecting versions < 0.4.0. It is fixed in 0.4.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2022-0317? CVE-2022-0317 has a CVSS score of 4.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.
Which versions of github.com/google/go-attestation are affected by CVE-2022-0317? github.com/google/go-attestation (go) versions < 0.4.0 is affected.
Is there a fix for CVE-2022-0317? Yes. CVE-2022-0317 is fixed in 0.4.0. Upgrade to this version or later.
Is CVE-2022-0317 exploitable, and should I be worried? Whether CVE-2022-0317 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 CVE-2022-0317 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 CVE-2022-0317? Upgrade github.com/google/go-attestation to 0.4.0 or later.

Other vulnerabilities in github.com/google/go-attestation

CVE-2022-0317