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

[🐸 Frogbot] Update version of github.com/golang-jwt/jwt/v4 to 4.5.2 #398

Open
wants to merge 3 commits into
base: dev
Choose a base branch
from

Conversation

github-actions[bot]
Copy link

🚨 This automated pull request was created by Frogbot and fixes the below:

📦 Vulnerable Dependencies

Severity ID Contextual Analysis Direct Dependencies Impacted Dependency Fixed Versions
high
High
CVE-2025-30204 Not Covered github.com/golang-jwt/jwt/v4:v4.5.1
github.com/jfrog/jfrog-cli-artifactory:v0.2.1
github.com/jfrog/jfrog-cli-core/v2:v2.58.2
github.com/jfrog/jfrog-client-go:v1.51.1
github.com/golang-jwt/jwt/v4 v4.5.1 [4.5.2]

🔖 Details

Vulnerability Details

Contextual Analysis: Not Covered
Direct Dependencies: github.com/golang-jwt/jwt/v4:v4.5.1, github.com/jfrog/jfrog-cli-artifactory:v0.2.1, github.com/jfrog/jfrog-cli-core/v2:v2.58.2, github.com/jfrog/jfrog-client-go:v1.51.1
Impacted Dependency: github.com/golang-jwt/jwt/v4:v4.5.1
Fixed Versions: [4.5.2]
CVSS V3: 7.5

golang-jwt is a Go implementation of JSON Web Tokens. Prior to
5.2.2 and 4.5.2, the function parse.ParseUnverified 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. This issue is fixed in 5.2.2 and 4.5.2.


@hadarshjfrog hadarshjfrog added the safe to test Approve running integration tests on a pull request label Mar 27, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Mar 27, 2025
Copy link
Author

👍 Frogbot scanned this pull request and did not find any new security issues.


@hadarshjfrog hadarshjfrog added the safe to test Approve running integration tests on a pull request label Mar 27, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Mar 27, 2025
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.

2 participants