cve.bz

CVE-2023-27584 linuxfoundation dragonfly: Use of Hard-coded Credentials

9.8 criticalExploit referenceEPSS 34%Fix available

Critical (9.8) in linuxfoundation dragonfly. EPSS 34% estimated probability of exploitation activity in the next 30 days. Fixed in d7y.io/dragonfly/v2 2.0.9-rc.2, 2.1.0-beta.1.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
34% (unchanged from 34% a week ago; 34% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2024-09-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-798 Use of Hard-coded Credentials
CWE-321 Use of Hard-coded Cryptographic Key
OWASP Top 10
A04:2025 Cryptographic Failures, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-27584 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-27584?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-27584?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-27584 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:dragonflybefore 2.0.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hpc8-7wpm-889wGod7y.io/dragonfly/v2>=2.1.0-alpha.0 <2.1.0-beta.12.1.0-beta.1
GHSA-hpc8-7wpm-889wGod7y.io/dragonfly/v2<2.0.9-rc.22.0.9-rc.2
GO-2024-3136God7y.io/dragonfly/v2<2.1.0-beta.12.1.0-beta.1

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-70 Try Common or Default Usernames and Passwords Likelihood: Medium · Severity: High
  • CAPEC-191 Read Sensitive Constants Within an Executable Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON