Skip to content
Fencer Intel
critical 9.8

CVE-2023-27584 in the critical feed json

Dragonfly2 vulnerable to hard coded cyptographic key

published 2y ago modified 4mo ago also GHSA-hpc8-7wpm-889w , GO-2024-3136 , EUVD-2024-2812

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
33.9%
EPSS 33.9% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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.

Patch / fix

  • go d7y.io/dragonfly/v2 2.0.9-rc.2, 2.1.0-beta.1
  • dragonflyoss Dragonfly2 2.0.9

Is CVE-2023-27584 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

33.87% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

  • github.com https://github.com/dragonflyoss/Dragonfly2/security/advisories/GHSA-hpc8-7wpm-889w referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go d7y.io/dragonfly/v2
>=2.1.0-alpha.0, <2.1.0-beta.1
<2.0.9-rc.2
<2.1.0-beta.1
2.1.0-beta.1
2.0.9-rc.2

Affected products

  • dragonflyoss Dragonfly2

Classification

Weakness
  • CWE-321 Use of Hard-coded Cryptographic Key
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.