GHSA-h72h-ppcx-998p: Zebra has pre-handshake buffer capacity reservation based on attacker-claimed body length
Zebra versions up to and including v4.4.1 have a vulnerability where the P2P codec reserves virtual buffer capacity based on an attacker-claimed body length before handshake completion. This reservation affects only virtual address space without committing physical memory, and existing connection limits and handshake timeouts mitigate practical exploitation. The issue is addressed by deferring large buffer reservations until after the handshake or capping pre-handshake message reservations. The impact is minimal and does not cause measurable denial-of-service.
AI Analysis
Technical Summary
The vulnerability exists in Zebra's P2P codec where the decode method reserves buffer capacity based on the body length field claimed by an attacker in the protocol header before the handshake completes. This reservation can be up to approximately 2 MiB of virtual memory per connection. However, since physical memory is not allocated until data is written, and the attacker can avoid sending body bytes, the impact on actual memory usage is negligible. Zebra's mitigations, including per-IP connection limits, accept rate limits, and handshake timeouts, further reduce the attack surface. The fix involves deferring large buffer reservations until after handshake completion or limiting reservation size for pre-handshake messages.
Potential Impact
The vulnerability only affects virtual address space reservation without allocating physical memory, resulting in minimal impact. Existing mitigations such as limiting connections per IP, handshake timeouts, and connection accept rates effectively prevent practical denial-of-service. There is no measurable increase in resource usage or service disruption demonstrated by the reporter's proof of concept.
Mitigation Recommendations
A fix is available that defers large buffer reservations until after handshake completion or caps the reservation size for pre-handshake messages. No workaround is necessary as existing per-IP connection limits, handshake timeouts, and accept rate limits effectively mitigate the practical impact. Users should apply the official fix when available to improve defense-in-depth.
GHSA-h72h-ppcx-998p: Zebra has pre-handshake buffer capacity reservation based on attacker-claimed body length
Description
Zebra versions up to and including v4.4.1 have a vulnerability where the P2P codec reserves virtual buffer capacity based on an attacker-claimed body length before handshake completion. This reservation affects only virtual address space without committing physical memory, and existing connection limits and handshake timeouts mitigate practical exploitation. The issue is addressed by deferring large buffer reservations until after the handshake or capping pre-handshake message reservations. The impact is minimal and does not cause measurable denial-of-service.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in Zebra's P2P codec where the decode method reserves buffer capacity based on the body length field claimed by an attacker in the protocol header before the handshake completes. This reservation can be up to approximately 2 MiB of virtual memory per connection. However, since physical memory is not allocated until data is written, and the attacker can avoid sending body bytes, the impact on actual memory usage is negligible. Zebra's mitigations, including per-IP connection limits, accept rate limits, and handshake timeouts, further reduce the attack surface. The fix involves deferring large buffer reservations until after handshake completion or limiting reservation size for pre-handshake messages.
Potential Impact
The vulnerability only affects virtual address space reservation without allocating physical memory, resulting in minimal impact. Existing mitigations such as limiting connections per IP, handshake timeouts, and connection accept rates effectively prevent practical denial-of-service. There is no measurable increase in resource usage or service disruption demonstrated by the reporter's proof of concept.
Mitigation Recommendations
A fix is available that defers large buffer reservations until after handshake completion or caps the reservation size for pre-handshake messages. No workaround is necessary as existing per-IP connection limits, handshake timeouts, and accept rate limits effectively mitigate the practical impact. Users should apply the official fix when available to improve defense-in-depth.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-h72h-ppcx-998p
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["crates.io"]
- Database Specific Severity
- LOW
- Cvss Version
- 3.1
Threat ID: 6a46ecb727e9c7971943ca19
Added to database: 07/02/2026, 22:56:55 UTC
Last enriched: 07/02/2026, 23:11:38 UTC
Last updated: 07/03/2026, 03:36:14 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.