Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented May 21, 2025

This PR contains the following updates:

Package Change Age Confidence
gopkg.in/go-jose/go-jose.v2 v2.6.2v2.6.3 age confidence

GitHub Vulnerability Alerts

CVE-2024-28180

Impact

An attacker could send a JWE containing compressed data that used large amounts of memory and CPU when decompressed by Decrypt or DecryptMulti. Those functions now return an error if the decompressed data would exceed 250kB or 10x the compressed size (whichever is larger). Thanks to Enze Wang@Alioth and Jianjun Chen@Zhongguancun Lab (@​zer0yu and @​chenjj) for reporting.

Patches

The problem is fixed in the following packages and versions:

  • github.com/go-jose/go-jose/v4 version 4.0.1
  • github.com/go-jose/go-jose/v3 version 3.0.3
  • gopkg.in/go-jose/go-jose.v2 version 2.6.3

The problem will not be fixed in the following package because the package is archived:

  • gopkg.in/square/go-jose.v2

Release Notes

go-jose/go-jose (gopkg.in/go-jose/go-jose.v2)

v2.6.3: Version 2.6.3

Compare Source

Fixed

  • Limit decompression output size to prevent a DoS. Backport from v4.0.1.

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 added the security label May 21, 2025
@renovate renovate bot requested a review from pyshx as a code owner May 21, 2025 07:03
@coderabbitai
Copy link

coderabbitai bot commented May 21, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@netlify
Copy link

netlify bot commented May 21, 2025

Deploy Preview for reearth-classic canceled.

Name Link
🔨 Latest commit b9e2a9c
🔍 Latest deploy log https://app.netlify.com/projects/reearth-classic/deploys/682d7ababa064b0008459e1c

@codecov
Copy link

codecov bot commented May 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 23.79%. Comparing base (703e022) to head (1e6a17d).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main      #63      +/-   ##
==========================================
- Coverage   23.80%   23.79%   -0.01%     
==========================================
  Files        1587     1588       +1     
  Lines      170092   170141      +49     
  Branches     2801     2801              
==========================================
  Hits        40486    40486              
- Misses     128439   128488      +49     
  Partials     1167     1167              
Flag Coverage Δ
server 32.02% <ø> (-0.05%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot force-pushed the renovate/go-gopkg.in-go-jose-go-jose.v2-vulnerability branch from b9e2a9c to 59db7ec Compare August 11, 2025 04:04
@renovate renovate bot force-pushed the renovate/go-gopkg.in-go-jose-go-jose.v2-vulnerability branch from 59db7ec to 311cdb7 Compare September 26, 2025 00:02
@renovate renovate bot force-pushed the renovate/go-gopkg.in-go-jose-go-jose.v2-vulnerability branch 3 times, most recently from 5c6e5f5 to 502ba85 Compare November 27, 2025 08:19
@renovate renovate bot requested a review from soneda-yuya as a code owner November 27, 2025 08:19
@renovate renovate bot force-pushed the renovate/go-gopkg.in-go-jose-go-jose.v2-vulnerability branch 7 times, most recently from 486d50b to c9cdf87 Compare December 5, 2025 06:15
@renovate renovate bot force-pushed the renovate/go-gopkg.in-go-jose-go-jose.v2-vulnerability branch 2 times, most recently from 72e5e70 to 1e6a17d Compare December 24, 2025 05:57
@renovate renovate bot force-pushed the renovate/go-gopkg.in-go-jose-go-jose.v2-vulnerability branch from 1e6a17d to 6a04da0 Compare January 7, 2026 04:49
@renovate renovate bot force-pushed the renovate/go-gopkg.in-go-jose-go-jose.v2-vulnerability branch from 6a04da0 to 03583e4 Compare January 8, 2026 01:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant