Memory handling vulnerability in ProtocolBuffers Java core and lite
Google LLC Protocolbuffers
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| com.google.protobuf:protobuf-java Maven |
|
|
Google LLC Protocolbuffers
| Product | Affected | Fixed in |
|---|---|---|
| com.google.protobuf:protobuf-java Maven |
|
|
| com.google.protobuf:protobuf-kotlin Maven |
|
|
| google-protobuf RubyGems |
|
|
| com.google.protobuf:protobuf-javalite Maven |
|
|
| com.google.protobuf:protobuf-kotlin-lite Maven |
|
|
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.
From the CVE record · Google
Affected Protocolbuffers packages can spend excessive time in garbage collection when parsing binary input containing multiple non-repeated embedded messages with repeated or unknown fields. An attacker who can supply such input could cause a denial of service. The input does not specify whether network access, authentication, or user interaction is required.
Teams using Maven protobuf-java, protobuf-kotlin, protobuf-javalite, or protobuf-kotlin-lite, or RubyGems google-protobuf, should check for affected versions below 3.16.3 or in the listed pre-fix 3.17–3.21 release ranges.