chore(deps): update dependency gitleaks/gitleaks to v8.24.0

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
gitleaks/gitleaks	minor	8.23.3 -> 8.24.0

---

Warning

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

---

Release Notes

gitleaks/gitleaks (gitleaks/gitleaks)

v8.24.0

Compare Source

Changelog

• c2afd56 Make paths and fingerprints platform-agnostic (#​1622)
• 818e32f Add Sonar rule (#​1756)
• 3fa5a3a Minor false positive improvements (#​1758)
• 2020e6a Add support for streaming DetectReader (#​1760)
• 9122a2d chore: Update github.com/wasilibs/go-re2 to v1.9.0 (#​1763)
• 398d0c4 docs: describe extended rules take precedence over base rules (#​1563)
• ae26eff feat(git): disable link generation (#​1748)
• c6424a6 added sourcegraph token rule (#​1736)
• 6411402 feat(config): add rule for .p12 files (#​1738)
• d71d95d add deno.lock to default exclusions (#​1740)

---

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.

[nicholasdille-bot]

Auto-approved because label type/renovate is present.

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/gitleaks:8.24.0

📦 Image Reference ghcr.io/uniget-org/tools/gitleaks:8.24.0

digest	sha256:3dc5855288da596c1df268faf476efbc62899389b9ac1f3fb490e4a78ea132bb
vulnerabilities
platform	linux/amd64
size	5.4 MB
packages	47

golang.org/x/crypto 0.29.0 (golang) pkg:golang/golang.org/x/crypto@0.29.0 Improper Authorization Affected range <0.31.0 Fixed version 0.31.0 CVSS Score 9.1 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Description Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

stdlib 1.23.3 (golang) pkg:golang/stdlib@1.23.3 Affected range >=1.23.0-0 <1.23.5 Fixed version 1.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. Affected range >=1.23.0-0 <1.23.5 Fixed version 1.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. Affected range >=1.23.0-0 <1.23.6 Fixed version 1.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.

[github-actions]

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

[github-actions]

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