fix(deps): Update dependency protobuf to v6.33.5 [SECURITY] - abandoned#709
fix(deps): Update dependency protobuf to v6.33.5 [SECURITY] - abandoned#709renovate-bot wants to merge 2 commits into
Conversation
|
/gcbrun |
There was a problem hiding this comment.
Code Review
This pull request updates the protobuf dependency to version 6.33.5 across multiple requirements.txt files. A review comment identifies that the source requirements.in file for the american-option module still pins the older version, which will cause this update to be lost during the next dependency compilation. Additionally, the reviewer notes a potential compatibility issue between the new protobuf version and the current grpcio-tools version, suggesting that both should be updated in tandem or a different version of protobuf should be selected to ensure stability.
| --hash=sha256:a109916aaac42bff84702fb5187f3edadbc7c97fc2c99c5ff81dd15dcce0d1e5 \ | ||
| --hash=sha256:b848dbe1d57ed7c191dfc4ea64b8b004a3f9ece4bf4d0d80a367b76df20bf36e \ | ||
| --hash=sha256:f3ecdef226b9af856075f28227ff2c90ce3a594d092c39bee5513573f25e2714 | ||
| protobuf==6.33.5 \ |
There was a problem hiding this comment.
The requirements.in file for this module still pins protobuf==5.27.2 (line 19). Since requirements.txt is autogenerated from it, this security update will be lost upon the next re-compilation. Furthermore, the comment in requirements.in (line 17) states that protobuf and grpcio-tools must be kept in sync. Upgrading to 6.33.5 while keeping grpcio-tools at 1.66.1 may lead to compatibility issues. Consider updating both in requirements.in to their latest versions (e.g., grpcio-tools==1.70.0 and protobuf==6.33.5), or if a major version jump is not desired, update protobuf to 5.29.5 which also contains the security fixes.
Restricted GKE Standard clusters and ARM node pools to zones supporting nvidia-tesla-t4 and t2a-standard-4 hardware. Replaced hardcoded us-central1 zones with dynamic discovery using google_compute_zones and google_compute_machine_types data sources.
5401800 to
9dd6c3f
Compare
|
/gcbrun |
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
==6.30.0→==6.33.5==5.27.2→==6.33.5protobuf-python has a potential Denial of Service issue
CVE-2025-4565 / GHSA-8qvm-5x2c-j2w7
More information
Details
Summary
Any project that uses Protobuf pure-Python backend to parse untrusted Protocol Buffers data containing an arbitrary number of recursive groups, recursive messages or a series of
SGROUPtags can be corrupted by exceeding the Python recursion limit.Reporter: Alexis Challande, Trail of Bits Ecosystem Security Team
ecosystem@trailofbits.com
Affected versions: This issue only affects the pure-Python implementation of protobuf-python backend. This is the implementation when
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=pythonenvironment variable is set or the default when protobuf is used from Bazel or pure-Python PyPi wheels. CPython PyPi wheels do not use pure-Python by default.This is a Python variant of a previous issue affecting protobuf-java.
Severity
This is a potential Denial of Service. Parsing nested protobuf data creates unbounded recursions that can be abused by an attacker.
Proof of Concept
For reproduction details, please refer to the unit tests decoder_test.py and message_test
Remediation and Mitigation
A mitigation is available now. Please update to the latest available versions of the following packages:
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
protobuf affected by a JSON recursion depth bypass
CVE-2026-0994 / GHSA-7gcm-g887-7qv7
More information
Details
A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages.
Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
🚦 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.