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: update module github.com/go-jose/go-jose/v4 to v4.0.5 [security] #960

Closed

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 25, 2025

Update Request | Renovate Bot

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/go-jose/go-jose/v4 v4.0.4 -> v4.0.5 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2025-27144

Impact

When parsing compact JWS or JWE input, go-jose could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of '.' characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service.

Patches

Version 4.0.5 fixes this issue

Workarounds

Applications could pre-validate payloads passed to go-jose do not contain an excessive number of '.' characters.

References

This is the same sort of issue as in the golang.org/x/oauth2/jws package as CVE-2025-22868 and Go issue https://go.dev/issue/71490.


Release Notes

go-jose/go-jose (github.com/go-jose/go-jose/v4)

v4.0.5

Compare Source

What's Changed

Fixes GHSA-c6gw-w398-hv78

Various other dependency updates, small fixes, and documentation updates in the full changelog

New Contributors

Full Changelog: go-jose/go-jose@v4.0.4...v4.0.5


Configuration

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

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

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 force-pushed the renovate/go-github.com-go-jose-go-jose-v4-vulnerability branch 15 times, most recently from a7d3d8d to bc29f1c Compare March 4, 2025 16:34
@renovate renovate bot force-pushed the renovate/go-github.com-go-jose-go-jose-v4-vulnerability branch 10 times, most recently from 10118b4 to 1224f80 Compare March 12, 2025 15:01
@renovate renovate bot changed the title chore: update module github.com/go-jose/go-jose/v4 to v4.0.5 [security] chore: update module github.com/go-jose/go-jose/v4 to v4.0.5 [security] - autoclosed Mar 12, 2025
@renovate renovate bot closed this Mar 12, 2025
@renovate renovate bot deleted the renovate/go-github.com-go-jose-go-jose-v4-vulnerability branch March 12, 2025 19:02
@renovate renovate bot changed the title chore: update module github.com/go-jose/go-jose/v4 to v4.0.5 [security] - autoclosed chore: update module github.com/go-jose/go-jose/v4 to v4.0.5 [security] Mar 12, 2025
@renovate renovate bot reopened this Mar 12, 2025
@renovate renovate bot force-pushed the renovate/go-github.com-go-jose-go-jose-v4-vulnerability branch 9 times, most recently from 7813cfa to 7ea504f Compare March 19, 2025 16:47
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/go-github.com-go-jose-go-jose-v4-vulnerability branch from 7ea504f to eef38d1 Compare March 19, 2025 19:37
@Unix4ever Unix4ever closed this Mar 20, 2025
Copy link
Author

renovate bot commented Mar 20, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v4.0.5). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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