All reports
Medium

Dragonfly incorrectly handles a task structure’s usedTrac field

Affected versions

Version ranges need review.

Affected versions
< 2.1.0
Fixed version
2.1.0
Affected versions
<2.1.0
Fixed version
2.1.0
Affected versions
*
Fixed version
Not reported
Affected versions
< 2.1.0
Fixed version
2.1.0

Exploitation

CVE-2025-59348

Probability of exploitation in the next 30 days: 0.36%

FIRST EPSS · 2026-11-20

Description

Impact

The processPieceFromSource method (figure 4.1) is part of a task processing mechanism. The method writes pieces of data to storage, updating a Task structure along the way. The 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.

var n int64
result.Size, err = pt.GetStorage().WritePiece([skipped])
result.FinishTime = time.Now().UnixNano()
if n > 0 {
       pt.AddTraffic(uint64(n))
}

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.

Patches
  • Dragonfy v2.1.0 and above.

Workarounds

There are no effective workarounds, beyond upgrading.

References

A third party security audit was performed by Trail of Bits, you can see the full report.

If you have any questions or comments about this advisory, please email us at dragonfly-maintainers@googlegroups.com.

Links

Credits

  • gaius-qi