Parsing issue in protobuf message-type extension
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.21.7, 3.20.3, 3.19.6, 3.16.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Google ProtocolBuffers
From 3.21.0 · fixed in 3.21.7; From 3.20.0 · fixed in 3.20.3; From 3.19.0 · fixed in 3.19.6; From 3.16.0 · fixed in 3.16.3
- com.google.protobuf:protobuf-javaMaven
From 3.0.0 · fixed in 3.16.3
- com.google.protobuf:protobuf-javaMaven
From 3.17.0 · fixed in 3.19.6
- com.google.protobuf:protobuf-javaMaven
From 3.20.0 · fixed in 3.20.3
- com.google.protobuf:protobuf-javaMaven
From 3.21.0 · fixed in 3.21.7
- com.google.protobuf:protobuf-javaliteMaven
From 3.0.0 · fixed in 3.16.3
- com.google.protobuf:protobuf-javaliteMaven
From 3.17.0 · fixed in 3.19.6
- com.google.protobuf:protobuf-javaliteMaven
From 3.20.0 · fixed in 3.20.3
- com.google.protobuf:protobuf-javaliteMaven
From 3.21.0 · fixed in 3.21.7