Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 18, 2023

This PR contains the following updates:

Package Change Age Confidence
protobuf ^3.15.8^4.0.0 age confidence
protobuf ==3.15.8==4.25.8 age confidence

GitHub Vulnerability Alerts

CVE-2022-1941

Summary

A message parsing and memory management vulnerability in ProtocolBuffer’s C++ and Python implementations can trigger an out of memory (OOM) failure when processing a specially crafted message, which could lead to a denial of service (DoS) on services using the libraries.

Reporter: ClusterFuzz

Affected versions: All versions of C++ Protobufs (including Python) prior to the versions listed below.

Severity & Impact

As scored by google
Medium 5.7 - CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Asscored byt NIST
High 7.5 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

A small (~500 KB) malicious payload can be constructed which causes the running service to allocate more than 3GB of RAM.

Proof of Concept

For reproduction details, please refer to the unit test that identifies the specific inputs that exercise this parsing weakness.

Mitigation / Patching

Please update to the latest available versions of the following packages:

  • protobuf-cpp (3.18.3, 3.19.5, 3.20.2, 3.21.6)
  • protobuf-python (3.18.3, 3.19.5, 3.20.2, 4.21.6)

CVE-2025-4565

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 SGROUP tags 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=python environment 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:

  • protobuf-python(4.25.8, 5.29.5, 6.31.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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 changed the title Update dependency protobuf to v3.18.3 [SECURITY] Update dependency protobuf to v3.18.3 [SECURITY] - autoclosed Nov 1, 2023
@renovate renovate bot closed this Nov 1, 2023
@renovate renovate bot deleted the renovate/pypi-protobuf-vulnerability branch November 1, 2023 02:36
@renovate renovate bot changed the title Update dependency protobuf to v3.18.3 [SECURITY] - autoclosed Update dependency protobuf to v3.18.3 [SECURITY] Nov 2, 2023
@renovate renovate bot reopened this Nov 2, 2023
@renovate renovate bot restored the renovate/pypi-protobuf-vulnerability branch November 2, 2023 08:41
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from cceae95 to dfe90c9 Compare November 2, 2023 08:41
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from dfe90c9 to d188a9c Compare August 10, 2024 05:54
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch 2 times, most recently from beaef2d to 46694c1 Compare November 4, 2024 02:48
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from 46694c1 to b191394 Compare January 15, 2025 03:58
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from b191394 to 408d6dd Compare January 31, 2025 16:21
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from 408d6dd to 565c6f7 Compare March 5, 2025 04:10
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch 2 times, most recently from 0515c2f to ddb1026 Compare March 18, 2025 20:13
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from ddb1026 to ab32400 Compare April 12, 2025 03:41
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from ab32400 to 28ce318 Compare May 9, 2025 00:22
@renovate renovate bot changed the title Update dependency protobuf to v3.18.3 [SECURITY] Update dependency protobuf to v4 [SECURITY] Jun 21, 2025
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from 28ce318 to 9590c3a Compare June 21, 2025 12:02
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from 9590c3a to 09a942c Compare September 11, 2025 08:13
@renovate renovate bot changed the title Update dependency protobuf to v4 [SECURITY] Update dependency protobuf to v6 [SECURITY] Sep 11, 2025
@renovate renovate bot changed the title Update dependency protobuf to v6 [SECURITY] Update dependency protobuf to v4 [SECURITY] Sep 14, 2025
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from 09a942c to 637badd Compare September 14, 2025 23:39
@renovate renovate bot force-pushed the renovate/pypi-protobuf-vulnerability branch from 637badd to dfaac06 Compare September 26, 2025 03:44
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