CVE-2023-27584: Dragonfly2 vulnerable to hard coded cyptographic key
Noroxi assessment
Priority: Plan (action score 49/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB / GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 33.8% (FIRST EPSS); higher than 98.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: d7y.io/dragonfly/v2 (Go) 2.1.0-beta.1, 2.0.9-rc.2.
Add it to your regular patch cycle. Upgrade to d7y.io/dragonfly/v2 (Go) 2.1.0-beta.1, 2.0.9-rc.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 33.8% · 98th percentile
- CWE
- CWE-321
Report tools
Action score
49
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 10 / 30 · 33.8%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · GitHub_M
- 9.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linuxfoundation | dragonfly | cpe:2.3:a:linuxfoundation:dragonfly |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
dragonflyoss Dragonfly2
- < 2.0.9affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linuxfoundation dragonflybefore 2.0.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | d7y.io/dragonfly/v2 | from 2.1.0-alpha.0 · before 2.1.0-beta.1 | 2.1.0-beta.1 |
| Go | d7y.io/dragonfly/v2 | before 2.0.9-rc.2 | 2.0.9-rc.2 |
| Go | d7y.io/dragonfly/v2 | before 2.1.0-beta.1 | 2.1.0-beta.1 |
Same product
linuxfoundation: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-24124Dragonfly Manager Job API Allows Unauthenticated Access35Monitor
- CVE-2025-59353Manager generates mTLS certificates for arbitrary IP addresses30Monitor
- CVE-2025-59345Dragonfly did not enable authentication for some Manager’s endpoints30Monitor
Published before and after this one in the same product
- Later →CVE-2025-59346Sep 17, 2025 · Dragonfly server-side request forgery vulnerability22Monitor
- Later →CVE-2025-59347Sep 17, 2025 · Dragonfly Manager makes requests to external endpoints with disabled TLS authentication10Monitor
- Later →CVE-2025-59348Sep 17, 2025 · Dragonfly incorrectly handles a task structure’s usedTraffic field22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:d7y.io/dragonfly/v2 | 2.0.9-rc.2 | Package registry (OSV) |
| Go:d7y.io/dragonfly/v2 | 2.1.0-beta.1 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Nuclei detection template ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2023-27584 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-321 · Use of Hard-coded Cryptographic KeyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.