Parsing issue in protobuf message-type extension
Google ProtocolBuffers
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| com.google.protobuf:protobuf-java Maven |
|
|
Google ProtocolBuffers
| Product | Affected | Fixed in |
|---|---|---|
| com.google.protobuf:protobuf-java Maven |
|
|
| com.google.protobuf:protobuf-javalite Maven |
|
|
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.
From the CVE record · Google
A parsing issue in protobuf-java core and lite Message-Type Extensions can cause long garbage collection pauses and denial of service. This occurs when parsing inputs with multiple non-repeated embedded messages containing repeated or unknown fields. The input does not specify whether network access, authentication, or user interaction is required.
Engineers using Maven com.google.protobuf:protobuf-java or com.google.protobuf:protobuf-javalite in the listed affected ranges from 3.0.0 through versions before 3.21.7 should check their dependencies.