Skip to content

Protobuf Java vulnerable to Uncontrolled Resource Consumption

High severity GitHub Reviewed Published Dec 12, 2022 to the GitHub Advisory Database • Updated Sep 2, 2025

Package

maven com.google.protobuf:protobuf-java (Maven)

Affected versions

>= 3.17.0, < 3.19.6
>= 3.20.0, < 3.20.3
>= 3.21.0, < 3.21.7
>= 3.0.0, < 3.16.3

Patched versions

3.19.6
3.20.3
3.21.7
3.16.3
maven com.google.protobuf:protobuf-javalite (Maven)
>= 3.17.0, < 3.19.6
>= 3.20.0, < 3.20.3
>= 3.21.0, < 3.21.7
>= 3.0.0, < 3.16.3
3.19.6
3.20.3
3.21.7
3.16.3

Description

A parsing issue similar to CVE-2022-3171, but with Message-Type Extensions in protobuf-java core and lite versions prior to 3.21.7, 3.20.3, 3.19.6 and 3.16.3 can lead to a denial of service attack. Inputs containing multiple instances of non-repeated embedded messages with repeated or unknown fields causes objects to be converted back-n-forth between mutable and immutable forms, resulting in potentially long garbage collection pauses. We recommend updating to the versions mentioned above.

References

Published by the National Vulnerability Database Dec 12, 2022
Published to the GitHub Advisory Database Dec 12, 2022
Reviewed Dec 12, 2022
Last updated Sep 2, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(18th percentile)

Weaknesses

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Learn more on MITRE.

CVE ID

CVE-2022-3510

GHSA ID

GHSA-4gg5-vx3j-xwc7

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.