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

Added gama #10780

Merged
merged 1 commit into from
Mar 10, 2025
Merged

Added gama #10780

merged 1 commit into from
Mar 10, 2025

Conversation

nicholasdille
Copy link
Contributor

No description provided.

Copy link

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/gama:1.2.1

📦 Image Reference ghcr.io/uniget-org/tools/gama:1.2.1
digestsha256:156d101664d7131f6843b5bff76514e85f3da8d1b982f4d1df809c82a95bcd10
vulnerabilitiescritical: 0 high: 0 medium: 3 low: 0
platformlinux/amd64
size3.4 MB
packages35
critical: 0 high: 0 medium: 3 low: 0 stdlib 1.23.4 (golang)

pkg:golang/stdlib@1.23.4

medium : CVE--2024--45341

Affected range>=1.23.0-0
<1.23.5
Fixed version1.23.5
Description

A certificate with a URI which has a IPv6 address with a zone ID may incorrectly satisfy a URI name constraint that applies to the certificate chain.

Certificates containing URIs are not permitted in the web PKI, so this only affects users of private PKIs which make use of URIs.

medium : CVE--2024--45336

Affected range>=1.23.0-0
<1.23.5
Fixed version1.23.5
Description

The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com.

In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.

medium : CVE--2025--22866

Affected range>=1.23.0-0
<1.23.6
Fixed version1.23.6
Description

Due to the usage of a variable time instruction in the assembly implementation of an internal function, a small number of bits of secret scalars are leaked on the ppc64le architecture. Due to the way this function is used, we do not believe this leakage is enough to allow recovery of the private key when P-256 is used in any well known protocols.

Copy link

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/13760710553.

Copy link

PR is blocked and can not be merged. See https://github.com/uniget-org/tools/actions/runs/13760710553.

@nicholasdille nicholasdille merged commit a10d746 into main Mar 10, 2025
9 checks passed
@nicholasdille nicholasdille deleted the gama branch March 10, 2025 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant