CVE-2022-29173Network attack vector

Software rollback via zero-based metadata version checks

Published May 5, 2022 · Updated Apr 23, 2025

Rollback protection failure in the go-tuf client before 0.3.0 allows remote attackers to make clients install older software. During non-root-role updates, the client compares new metadata against a zero default instead of previously trusted versions and trusts timestamp and snapshot files before validating referenced metadata versions. Exploitation requires control of update metadata delivered to a client and can replace a previously known release with older software, including software containing known vulnerabilities.

CVSS severity8.8
High
EPSS probability0.56%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Rollback protection failure in the go-tuf client before 0.3.0 allows remote attackers to make clients install older software. During non-root-role updates, the client compares new metadata against a zero default instead of previously trusted versions and trusts timestamp and snapshot files before validating referenced metadata versions. Exploitation requires control of update metadata delivered to a client and can replace a previously known release with older software, including software containing known vulnerabilities.

The record

CVE
CVE-2022-29173
Published
May 5, 2022
Updated
Apr 23, 2025
Vendor
The Update Framework
Product
go-tuf
Classifications
CWE-354, T1565.002
Attack vector
network
Privileges
Unavailable

Timeline

How it unfolded

  1. May 5, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 23, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.3.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesUnavailable in this record.

What is affected?

The Update Framework · go-tufversion=< 0.3.0

Published CVSS scores

8.0GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
4.3NIST NVDAV:N/AC:M/Au:N/C:N/I:P/A:N
8.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-354Improper Validation of Integrity Check Value
T1565.002Data Manipulation: Transmitted Data Manipulation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo