Elasticsearch Packetbeat has Excessive Allocation of Memory and CPU via Malicious IPv4 Fragments
Elastic Packetbeat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/elastic/beats Go |
|
|
| github.com/elastic/beats/v7 |
Elastic Packetbeat
| Product | Affected | Fixed in |
|---|---|---|
| github.com/elastic/beats Go |
|
|
| github.com/elastic/beats/v7 |
|
|
Allocation of resources without limits or throttling (CWE-770) allows an unauthenticated remote attacker to cause excessive allocation (CAPEC-130) of memory and CPU via the integration of malicious IPv4 fragments, leading to a degradation in Packetbeat.
From the CVE record · elastic
Packetbeat does not limit resource allocation when integrating IPv4 fragments. An unauthenticated remote attacker can send malicious fragments that cause excessive memory and CPU use, degrading Packetbeat.
Engineers running Elastic Packetbeat with github.com/elastic/beats versions >=8.6.0 <8.19.9, >=9.0.0 <9.1.9, or >=9.2.0 <9.2.3, or github.com/elastic/beats/v7 versions before 7.0.0-alpha2.0.20251209162832-28cfc80d2f4e, should check their deployments.