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

Published Jan 25, 2022
·
Updated

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.

Patches 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.

Other sources

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.

Affected Software

2 affected componentsFixes available
go/github.com/google/go-attestation<0.4.0
0.4.0
Google go-attestation<0.3.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/google/go-attestation to a version that resolves this vulnerability.

    Fixed in 0.4.0
  2. Upgrade

    Upgrade go-attestation to a version that resolves this vulnerability.

    Fixed in 0.4.0
  3. Configuration

    When verifying PCRs using multiple quotes, use the new AKPublic.VerifyAll() method instead of AKPublic.Verify.

    go-attestation AKPublic verification method = VerifyAll

Event History

Feb 1, 2022
Advisory Published
12:43 AM
Feb 4, 2022
CVE Published
via MITRE·10:33 PM
Data Sourced
via MITRE·10:33 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the vulnerability ID for this vulnerability?

The vulnerability ID for this vulnerability is CVE-2022-0317.

2

What is the severity of CVE-2022-0317?

The severity of CVE-2022-0317 is medium with a severity value of 4.

3

What is the impact of CVE-2022-0317?

CVE-2022-0317 allows local users to provide a maliciously-formed Quote over no/some PCRs, causing `AKPublic.Verify` to succeed despite the inconsistency and subsequent use of the same set of PCR values in `Eventlog.Verify` lacks th…

4

What software is affected by CVE-2022-0317?

The affected software is go-attestation before version 0.4.0.

5

How do I fix CVE-2022-0317?

To fix CVE-2022-0317, upgrade to version 0.4.0 of go-attestation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203