Summary
protobuf-java has a potential Denial of Service issue
A potential Denial of Service issue in protobuf-java core and lite was discovered in the parsing procedure for binary and text format data. Input streams 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.
Reporter: OSS Fuzz
Affected versions: This issue affects both the Java full and lite Protobuf runtimes, as well as Protobuf for Kotlin and JRuby, which themselves use the Java Protobuf runtime.
Severity
CVE-2022-3171 Medium - CVSS Score: 5.7 (NOTE: there may be a delay in publication)
Remediation and Mitigation
Please update to the latest available versions of the following packages:
protobuf-java (3.21.7, 3.20.3, 3.19.6, 3.16.3)
protobuf-javalite (3.21.7, 3.20.3, 3.19.6, 3.16.3)
protobuf-kotlin (3.21.7, 3.20.3, 3.19.6, 3.16.3)
protobuf-kotlin-lite (3.21.7, 3.20.3, 3.19.6, 3.16.3)
google-protobuf [JRuby gem only] (3.21.7, 3.20.3, 3.19.6)
Impact
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
CVE-2022-3171 has a CVSS score of 5.7 (Medium). The vector is reachable from an adjacent network, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.21.7, 3.20.3, 3.19.6, 3.16.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
com.google.protobuf:protobuf-java to 3.21.7 or later; com.google.protobuf:protobuf-kotlin to 3.21.7 or later; google-protobuf to 3.21.7 or later; com.google.protobuf:protobuf-javalite to 3.21.7 or later; com.google.protobuf:protobuf-kotlin-lite to 3.21.7 or later; com.google.protobuf:protobuf-java to 3.20.3 or later; com.google.protobuf:protobuf-java to 3.19.6 or later; com.google.protobuf:protobuf-java to 3.16.3 or later; com.google.protobuf:protobuf-kotlin to 3.20.3 or later; com.google.protobuf:protobuf-kotlin to 3.19.6 or later; com.google.protobuf:protobuf-kotlin to 3.16.3 or later; google-protobuf to 3.20.3 or later; google-protobuf to 3.19.6 or later; google-protobuf to 3.16.3 or later; com.google.protobuf:protobuf-javalite to 3.20.3 or later; com.google.protobuf:protobuf-javalite to 3.19.6 or later; com.google.protobuf:protobuf-javalite to 3.16.3 or later; com.google.protobuf:protobuf-kotlin-lite to 3.20.3 or later; com.google.protobuf:protobuf-kotlin-lite to 3.19.6 or later; com.google.protobuf:protobuf-kotlin-lite to 3.16.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2022-3171? CVE-2022-3171 is a medium-severity improper input validation vulnerability in com.google.protobuf:protobuf-java (maven), affecting versions >= 3.21.0-rc-1, < 3.21.7. It is fixed in 3.21.7, 3.20.3, 3.19.6, 3.16.3. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- How severe is CVE-2022-3171? CVE-2022-3171 has a CVSS score of 5.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2022-3171?
com.google.protobuf:protobuf-java(maven) (versions >= 3.21.0-rc-1, < 3.21.7)com.google.protobuf:protobuf-kotlin(maven) (versions >= 3.21.0-rc-1, < 3.21.7)google-protobuf(rubygems) (versions >= 3.21.0.rc.1, < 3.21.7)com.google.protobuf:protobuf-javalite(maven) (versions >= 3.21.0-rc-1, < 3.21.7)com.google.protobuf:protobuf-kotlin-lite(maven) (versions >= 3.21.0-rc-1, < 3.21.7)
- Is there a fix for CVE-2022-3171? Yes. CVE-2022-3171 is fixed in 3.21.7, 3.20.3, 3.19.6, 3.16.3. Upgrade to this version or later.
- Is CVE-2022-3171 exploitable, and should I be worried? Whether CVE-2022-3171 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-3171 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-3171?
- Upgrade
com.google.protobuf:protobuf-javato 3.21.7 or later - Upgrade
com.google.protobuf:protobuf-kotlinto 3.21.7 or later - Upgrade
google-protobufto 3.21.7 or later - Upgrade
com.google.protobuf:protobuf-javaliteto 3.21.7 or later - Upgrade
com.google.protobuf:protobuf-kotlin-liteto 3.21.7 or later - Upgrade
com.google.protobuf:protobuf-javato 3.20.3 or later - Upgrade
com.google.protobuf:protobuf-javato 3.19.6 or later - Upgrade
com.google.protobuf:protobuf-javato 3.16.3 or later - Upgrade
com.google.protobuf:protobuf-kotlinto 3.20.3 or later - Upgrade
com.google.protobuf:protobuf-kotlinto 3.19.6 or later - Upgrade
com.google.protobuf:protobuf-kotlinto 3.16.3 or later - Upgrade
google-protobufto 3.20.3 or later - Upgrade
google-protobufto 3.19.6 or later - Upgrade
google-protobufto 3.16.3 or later - Upgrade
com.google.protobuf:protobuf-javaliteto 3.20.3 or later - Upgrade
com.google.protobuf:protobuf-javaliteto 3.19.6 or later - Upgrade
com.google.protobuf:protobuf-javaliteto 3.16.3 or later - Upgrade
com.google.protobuf:protobuf-kotlin-liteto 3.20.3 or later - Upgrade
com.google.protobuf:protobuf-kotlin-liteto 3.19.6 or later - Upgrade
com.google.protobuf:protobuf-kotlin-liteto 3.16.3 or later
- Upgrade