Bug 2315960 (CVE-2024-47534)

Summary: CVE-2024-47534 go-tuf: Incorrect delegation lookups can make go-tuf download the wrong artifact
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: adudiak, agarcial, aoconnor, asegurap, bdettelb, bkabrda, dfreiber, doconnor, drow, dymurray, jburrell, jkoehler, jmatthew, kshier, lball, lgamliel, lsturman, luizcosta, ngough, nweather, omaciel, rbobbitt, rfreiman, rjohnson, stcannon, teagle, veshanka, vkumar, whayutin, yguenane, zkayyali
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the go-tuf package. Due to incorrect delegation lookups, the go-tuf client inconsistently traces the delegations. For example, if targets delegate to "A", and then to "B", and "B" delegates to "C", then the client should trace the delegations in the order "A", then "B", then "C", but it may incorrectly trace the delegations: "B" to "C" to "A". This may cause go-tuf to download the wrong artifact.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2024-10-01 16:03:20 UTC
go-tuf is a Go implementation of The Update Framework (TUF). The go-tuf client inconsistently traces the delegations. For example, if targets delegate to "A", and to "B", and "B" delegates to "C", then the client should trace the delegations in the order "A" then "B" then "C" but it may incorrectly trace the delegations "B"->"C"->"A". This vulnerability is fixed in 2.0.1.