Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Incorrect delegation lookups can make go-tuf download the wrong artifact

CVSS 4.0 8.2 HIGHEUVD CVSS 4.0 8.2 CVSS 4.0 · [email protected] · Secondary 8.2 HIGHCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by github.com/theupdateframework/go-tuf/v2 2.0.1osv · severity unknownFixed by github.com/theupdateframework/go-tuf/v2 2.0.1KEV status unknown

cve-program · CVE-2024-47534

Published

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.

Read the publisher's advisory

euvd · EUVD-2024-2931

Published

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.

Read the publisher's advisory

nvd · CVE-2024-47534

Published

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.

Read the publisher's advisory

osv · GHSA-4f8r-qqr9-fq8j

Published

During the ongoing work on the TUF conformance test suite, we have come across a test that reveals what we believe is a bug in go-tuf with security implications. The bug exists in go-tuf delegation tracing and could result in downloading the wrong artifact. We have come across this issue in the test in this PR: https://github.com/theupdateframework/tuf-conformance/pull/115. The test - `test_graph_traversal` - sets up a repository with a series of delegations, invokes the clients `refresh()` and then checks the order in which the client traced the delegations. The test shows that the go-tuf client inconsistently traces the delegations in a wrong way. For example, [during one CI run](https://github.com/theupdateframework/tuf-conformance/pull/115#issuecomment-2275625542), the `two-level-delegations` test case triggered a wrong order. The delegations in this look as such: ```python "two-level-delegations": DelegationsTestCase( delegations=[ DelegationTester("targets", "A"), DelegationTester("targets", "B"), DelegationTester("B", "C"), ], visited_order=["A", "B", "C"], ), ``` Here, `targets` delegate to `"A"`, and to `"B"`, and `"B"` delegates to `"C"`. The client should trace the delegations in the order `"A"` then `"B"` then `"C"` but in this particular CI run, go-tuf traced the delegations `"B"->"C"->"A"`. In a subsequent CI run, this test case did not fail, but [another one did](https://github.com/theupdateframework/tuf-conformance/pull/115#issuecomment-2275640487). @jku has done a bit of debugging and believes that the returned map of `GetRolesForTarget` returns a map that causes this behavior: https://github.com/theupdateframework/go-tuf/blob/f95222bdd22d2ac4e5b8ed6fe912b645e213c3b5/metadata/metadata.go#L565-L580 We believe that this map should be an ordered list instead of a map.

Read the publisher's advisory

osv · GO-2024-3166

Published

Incorrect delegation lookups can make go-tuf download the wrong artifact in github.com/theupdateframework/go-tuf

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2024-47534

Published

Incorrect delegation lookups can make go-tuf download the wrong artifact

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.

Source published
1 Oct 2024 15:17:47 UTC
Source modified
21 Nov 2024 16:56:38 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

euvd · EUVD-2024-2931

Published

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 delegation…

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 1, 2024, 3:17:47 PM

dateUpdated: Nov 21, 2024, 4:56:38 PM

3 related source bulletins · separate from aliases

openSUSE-SU-2024:0350-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-0132 · CVE-2024-0133 · CVE-2024-10005 · CVE-2024-10006 · CVE-2024-10086 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-10452 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-39720 · CVE-2024-46872 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47401 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50052 · CVE-2024-50312 · CVE-2024-50354 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8185 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

SUSE-SU-2024:3911-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

openSUSE-SU-2024:14447-1: govulncheck-vulndb-0.0.20241030T212825-1.1 on GA media

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

Source published
Oct 1, 2024, 3:17:47 PM (timezone not stated)
Source modified
Nov 21, 2024, 4:56:38 PM (timezone not stated)
Saved here
15 Nov 2026 08:28:19 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 4.0 · 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

nvd · CVE-2024-47534

Published

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 delegation…

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-362

Original publisher date fields

published: 2024-10-01T16:15:09.857

lastModified: 2026-06-17T07:57:15.433

Source published
1 Oct 2024 16:15:09 UTC
Source modified
17 Jun 2026 07:57:15 UTC
Saved here
25 Oct 2026 00:17:35 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · [email protected] · Secondary · 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

osv · GHSA-4f8r-qqr9-fq8j

Published

Incorrect delegation lookups can make go-tuf download the wrong artifact

During the ongoing work on the TUF conformance test suite, we have come across a test that reveals what we believe is a bug in go-tuf with security implications. The bug exists in go-tuf delegation tracing and could result in downloading the wrong artifact. We have come across this issue in the test in this PR: https://github.com/theupdateframework/tuf-conformance/pull/115. The test - `test_graph_traversal` - sets up a repository with a series of delegations, invokes the clients `refresh()` and then checks the order in which the client traced the delegations. The test shows that the go-tuf client inconsistently traces the delegations in a wrong way. For example, [during one CI run](https://github.com/theupdateframework/tuf-conformance/pull/115#issuecomment-2275625542), the `two-level-delegations` test case triggered a wrong order. The delegations in this look as such: ```python "two-level-delegations": DelegationsTestCase( delegations=[ DelegationTester("targets", "A"), DelegationTester("targets", "B"), DelegationTester("B", "C"), ], visited_order=["A", "B", "C"], ), ``` Here, `targets` delegate to `"A"`, and to `"B"`, and `"B"` delegates to `"C"`. The client should trace the delegations in the order `"A"` then `"B"` then `"C"` but in this particular CI run, go-tuf traced the delegations `"B"->"C"->"A"`. In a subsequent CI run, this test case did not fail, but [another one did](https://github.com/theupdateframework/tuf-conformance/pull/115#issuecomment-2275640487). @jku has done a bit of debugging and believes that the returned map of `GetRolesForTarget` returns a map that causes this behavior: https://github.com/theupdateframework/go-tuf/blob/f95222bdd22d2ac4e5b8ed6fe912b645e213c3b5/metadata/metadata.go#L565-L580 We believe that this map should be an ordered list instead of a map.

Source published
1 Oct 2024 18:13:25 UTC
Source modified
10 Sep 2026 03:50:19 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Publisher rating · HIGH

osv · GO-2024-3166

Published

Incorrect delegation lookups can make go-tuf download the wrong artifact in github.com/theupdateframework/go-tuf

Incorrect delegation lookups can make go-tuf download the wrong artifact in github.com/theupdateframework/go-tuf

Source published
9 Oct 2024 20:29:23 UTC
Source modified
4 Feb 2026 03:36:06 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 12:50 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current