Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency chainguard-dev/melange to v0.13.4 #7623

Merged
merged 1 commit into from
Oct 10, 2024

Conversation

uniget-bot
Copy link

This PR contains the following updates:

Package Update Change
chainguard-dev/melange patch 0.13.3 -> 0.13.4

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

chainguard-dev/melange (chainguard-dev/melange)

v0.13.4

Compare Source

What's Changed

Full Changelog: chainguard-dev/melange@v0.13.3...v0.13.4


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Copy link

@nicholasdille-bot nicholasdille-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because label type/renovate is present.

Copy link

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/melange:0.13.4

📦 Image Reference ghcr.io/uniget-org/tools/melange:0.13.4
digestsha256:6507f54df21c4cd821fde8cf8d485f2dc4a14ef8bb673eb39165d62b8afcd88a
vulnerabilitiescritical: 0 high: 3 medium: 0 low: 0
platformlinux/amd64
size31 MB
packages198
critical: 0 high: 2 medium: 0 low: 0 github.com/u-root/u-root 0.14.0 (golang)

pkg:golang/github.com/u-root/u-root@0.14.0

high 7.5: CVE--2020--7669 OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities

Affected range<=v7.0.0
Fixed versionNot Fixed
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Description

This affects all versions of package github.com/u-root/u-root/pkg/tarutil. It is vulnerable to both leading and non-leading relative path traversal attacks in tar file extraction.

high 7.5: CVE--2020--7665 OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities

Affected range<=7.0.0
Fixed versionNot Fixed
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Description

This affects all versions of package github.com/u-root/u-root/pkg/uzip. It is vulnerable to both leading and non-leading relative path traversal attacks in zip file extraction.

critical: 0 high: 1 medium: 0 low: 0 github.com/theupdateframework/go-tuf 0.7.0 (golang)

pkg:golang/github.com/theupdateframework/go-tuf@0.7.0

high 7.5: CVE--2024--47534 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Affected range<2.0.1
Fixed version2.0.1
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Description

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: theupdateframework/tuf-conformance#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, the two-level-delegations test case triggered a wrong order. The delegations in this look as such:

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

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

Copy link

Copy link

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/11266058541.

@github-actions github-actions bot merged commit bad77dd into main Oct 10, 2024
9 of 10 checks passed
@github-actions github-actions bot deleted the renovate/chainguard-dev-melange-0.13.x branch October 10, 2024 01:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants