Dragonfly incorrectly handles a task structure’s usedTraffic field
dragonflyoss dragonfly
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dragonflyoss/dragonfly Go |
|
|
| d7y.io/dragonfly/v2 Go |
|
|
dragonflyoss dragonfly
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dragonflyoss/dragonfly Go |
|
|
| d7y.io/dragonfly/v2 Go |
|
|
Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.1.0, the processPieceFromSource method does not update the structure’s usedTraffic field, because an uninitialized variable n is used as a guard to the AddTraffic method call, instead of the result.Size variable. A task is processed by a peer. The usedTraffic metadata is not updated during the processing. Rate limiting is incorrectly applied, leading to a denial-of-service condition for the peer. This vulnerability is fixed in 2.1.0.
From the CVE record · GitHub_M
Before 2.1.0, processPieceFromSource fails to update usedTraffic metadata while a peer processes a task. This can cause rate limiting to be applied incorrectly, leading to a denial of service for the peer. The input does not specify whether authentication, network access, or user interaction is required.
Teams running Dragonfly with Go package github.com/dragonflyoss/dragonfly or d7y.io/dragonfly/v2 before 2.1.0 should check their deployments.