Denial of Service in Google Guava
Published Apr 26, 2018 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
Denial of Service in Google Guava
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- RHSA-2018:2428 ↗
- RHSA-2018:2740 ↗
- RHSA-2018:2741 ↗
- RHSA-2018:2742 ↗
- RHSA-2018:2598 ↗
- RHSA-2018:2643 ↗
- RHSA-2018:2424 ↗
- RHSA-2018:2423 ↗
- RHSA-2018:2425 ↗
- RHSA-2018:2927 ↗
- 1041707 ↗
- RHSA-2018:2743 ↗
Record history
Published Apr 26, 2018 · Last refreshed Nov 3, 2026