Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2022-3509

HIGH

Protobuf Java vulnerable to Uncontrolled Resource Consumption

Also known asGHSA-g5ww-5jh7-63cx
Published
Dec 12, 2022
Updated
Apr 12, 2026
Affected
7 pkgs
Patched
7 / 7
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk42th percentile+0.44%
0.00%0.36%0.71%1.07%0.1%0.6%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

7 pkgs affected
com.google.protobuf:protobuf-javacom.google.protobuf:protobuf-javacom.google.protobuf:protobuf-javacom.google.protobuf:protobuf-javacom.google.protobuf:protobuf-javalitecom.google.protobuf:protobuf-javalitecom.google.protobuf:protobuf-javalite

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A parsing issue similar to CVE-2022-3171, but with textformat 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.

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.google.protobuf:protobuf-java3.0.0&&< 3.16.33.16.3
Mavencom.google.protobuf:protobuf-java3.17.0&&< 3.19.63.19.6
Mavencom.google.protobuf:protobuf-java3.20.0&&< 3.20.33.20.3
Mavencom.google.protobuf:protobuf-java3.21.0&&< 3.21.73.21.7
Mavencom.google.protobuf:protobuf-javalite3.20.0&&< 3.20.33.20.3
Mavencom.google.protobuf:protobuf-javalite3.21.0&&< 3.21.73.21.7

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.google.protobuf:protobuf-java. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update com.google.protobuf:protobuf-java to 3.16.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-3509 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2022-3509 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-3509. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A parsing issue similar to CVE-2022-3171, but with textformat 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.
O3 Security · Impact-Aware SCA

Is CVE-2022-3509 in your dependencies?

O3 detects CVE-2022-3509 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.