CVE-2022-3171
HIGHprotobuf-java has a potential Denial of Service issue
EPSS Exploitation Probability
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
com.google.protobuf:protobuf-java☕com.google.protobuf:protobuf-kotlin☕com.google.protobuf:protobuf-javalite☕com.google.protobuf:protobuf-kotlin-lite☕com.google.protobuf:protobuf-java☕com.google.protobuf:protobuf-java☕com.google.protobuf:protobuf-java☕com.google.protobuf:protobuf-kotlin+12 moreReal-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 with binary data 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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.google.protobuf:protobuf-java | ≥ 3.21.0-rc-1&&< 3.21.7 | 3.21.7 |
| ☕Maven | com.google.protobuf:protobuf-kotlin | ≥ 3.21.0-rc-1&&< 3.21.7 | 3.21.7 |
| ☕Maven | com.google.protobuf:protobuf-javalite | ≥ 3.21.0-rc-1&&< 3.21.7 | 3.21.7 |
| ☕Maven | com.google.protobuf:protobuf-kotlin-lite | ≥ 3.21.0-rc-1&&< 3.21.7 | 3.21.7 |
| ☕Maven | com.google.protobuf:protobuf-java | ≥ 3.20.0-rc-1&&< 3.20.3 | 3.20.3 |
| ☕Maven | com.google.protobuf:protobuf-java | ≥ 3.17.0-rc-1&&< 3.19.6 | 3.19.6 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update com.google.protobuf:protobuf-java to 3.21.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-3171 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2022-3171 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-3171. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-3171 in your dependencies?
O3 detects CVE-2022-3171 across Maven, RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.