CVE-2025-59350: Timing attacks against Proxy’s basic authentication are possible

Published Sep 17, 2025
·
Updated

Impact The access control mechanism for the Proxy feature uses simple string comparisons and is therefore vulnerable to timing attacks. An attacker may try to guess the password one character at a time by sending all possible characters to a vulnerable mechanism and measuring the comparison instruction’s execution times. The vulnerability is shown in figure 8.1, where both the username and password are compared with a short-circuiting equality operation.

golang if user != proxy.basicAuth.Username || pass != proxy.basicAuth.Password {

It is currently undetermined what an attacker may be able to do with access to the proxy password.

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.

Other sources

Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.1.0, the access control mechanism for the Proxy feature uses simple string comparisons and is therefore vulnerable to timing attacks. An attacker may try to guess the password one character at a time by sending all possible characters to a vulnerable mechanism and measuring the comparison instruction’s execution times. This vulnerability is fixed in 2.1.0.

MITRE

Affected Software

4 affected componentsFixes available
DragonFly DragonFly<2.1.0
linuxfoundation Dragonfly Go<2.1.0
go/d7y.io/dragonfly/v2<2.1.0
2.1.0
go/github.com/dragonflyoss/dragonfly<2.1.0
2.1.0

Event History

Sep 17, 2025
CVE Published
via MITRE·07:43 PM
Data Sourced
via MITRE·07:43 PM
DescriptionWeakness
Advisory Published
via GitHub·08:02 PM
Data Sourced
via GitHub·08:02 PM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-59350?

The severity of CVE-2025-59350 is high due to the potential for timing attacks against the access control mechanism.

2

How do I fix CVE-2025-59350?

To fix CVE-2025-59350, upgrade Dragonfly to version 2.1.0 or later where the vulnerability has been addressed.

3

What systems are affected by CVE-2025-59350?

CVE-2025-59350 affects versions of Dragonfly prior to 2.1.0.

4

What type of attack is possible with CVE-2025-59350?

CVE-2025-59350 is vulnerable to timing attacks which could allow an attacker to guess passwords effectively.

5

Is CVE-2025-59350 an open source vulnerability?

Yes, CVE-2025-59350 pertains to an open source software project, Dragonfly.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203