Security Digest · Vulnerability record
CVE-2023-27584: Dragonfly2 has hard coded cyptographic key
Dragonfly is an open source P2P-based file distribution and image acceleration system.
CVSS 9.3 Critical EPSS 33.9% · p98
Should you act?
High exploit likelihood
EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 33.9%, percentile 98: FIRST’s model estimates a 33.9% chance of exploitation activity in the next 30 days, higher than 98% of all scored CVEs (very high). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
d7y.io/dragonfly/v2(Go) >= 2.1.0-alpha.0, < 2.1.0-beta.1, fixed in 2.1.0-beta.1;d7y.io/dragonfly/v2(Go) < 2.0.9-rc.2, fixed in 2.0.9-rc.2. Check your lockfile, including transitive dependencies.
What it is
Dragonfly is an open source P2P-based file distribution and image acceleration system. It is hosted by the Cloud Native Computing Foundation (CNCF) as an Incubating Level Project. Dragonfly uses JWT to verify user. However, the secret key for JWT, "Secret Key", is hard coded, which leads to authentication bypass. An attacker can perform any action as a user with admin privileges. This issue has been addressed in release version 2.0.9. All users are advised to upgrade. There are no known workarounds for this vulnerability.
From the GitHub advisory
Summary Hello dragonfly maintainer team, I would like to report a security issue concerning your JWT feature.
Details Dragonfly uses JWT to verify user. However, the secret key for JWT, "Secret Key", is hard coded, which leads to authentication bypass
PoC Use code below to generate a jwt token
And send request with JWT above , you can still get data without restriction.
Impact An attacker can perform any action as a user with admin privileges.
Weakness type: CWE-321, CWE-798.
Product: d7y.io/dragonfly/v2 (Go) · Assigned by: GitHub_M · Published: 2024-09-19
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Go | d7y.io/dragonfly/v2 | >= 2.1.0-alpha.0, < 2.1.0-beta.1 | 2.1.0-beta.1 |
| Go | d7y.io/dragonfly/v2 | < 2.0.9-rc.2 | 2.0.9-rc.2 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| dragonflyoss | Dragonfly2 | < 2.0.9 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 3.1 | 9.8 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: none
- Privileges required: none (no login)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 33.87% probability of exploitation activity in the next 30 days; percentile 98.
Timeline
- — CVE record published by GitHub_M
- — GitHub-reviewed advisory GHSA-hpc8-7wpm-889w published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-hpc8-7wpm-889w github.com
- CVE.org record CVE-2023-27584 cve.org
- NVD entry CVE-2023-27584 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com