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

fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security] (release-0.32) #5438

Open
wants to merge 1 commit into
base: release-0.32
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 21, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/golang-jwt/jwt/v5 v5.2.1 -> v5.2.2 age adoption passing confidence

jwt-go allows excessive memory allocation during header parsing

CVE-2025-30204 / GHSA-mh63-6h87-95cp

More information

Details

Summary

Function parse.ParseUnverified currently splits (via a call to strings.Split) its argument (which is untrusted data) on periods.

As a result, in the face of a malicious request whose Authorization header consists of Bearer followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument), with a constant factor of about 16. Relevant weakness: CWE-405: Asymmetric Resource Consumption (Amplification)

Details

See parse.ParseUnverified

Impact

Excessive memory allocation

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

golang-jwt/jwt (github.com/golang-jwt/jwt/v5)

v5.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.2.1...v5.2.2


Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner March 21, 2025 22:12
@renovate renovate bot added the security label Mar 21, 2025
@renovate renovate bot requested a review from a team as a code owner March 21, 2025 22:12
@renovate renovate bot requested review from chenrui333 and nitrocode and removed request for a team March 21, 2025 22:12
@renovate renovate bot enabled auto-merge (squash) March 21, 2025 22:12
@renovate renovate bot requested a review from X-Guardian March 21, 2025 22:12
@dosubot dosubot bot added dependencies PRs that update a dependency file go Pull requests that update Go code labels Mar 21, 2025
@renovate renovate bot changed the title fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security] (release-0.32) fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security] (release-0.32) - autoclosed Mar 21, 2025
@renovate renovate bot closed this Mar 21, 2025
auto-merge was automatically disabled March 21, 2025 22:20

Pull request was closed

@renovate renovate bot deleted the renovate/release-0.32-go-github.com-golang-jwt-jwt-v5-vulnerability branch March 21, 2025 22:20
@renovate renovate bot changed the title fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security] (release-0.32) - autoclosed fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security] (release-0.32) Mar 22, 2025
@renovate renovate bot reopened this Mar 22, 2025
@renovate renovate bot force-pushed the renovate/release-0.32-go-github.com-golang-jwt-jwt-v5-vulnerability branch from af9d606 to 970753b Compare March 22, 2025 06:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies PRs that update a dependency file go Pull requests that update Go code security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants