Manager generates mTLS certificates for arbitrary IP addresses
dragonflyoss dragonfly
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dragonflyoss/dragonfly Go |
|
|
| d7y.io/dragonfly/v2 Go |
|
|
dragonflyoss dragonfly
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dragonflyoss/dragonfly Go |
|
|
| d7y.io/dragonfly/v2 Go |
|
|
Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.1.0, a peer can obtain a valid TLS certificate for arbitrary IP addresses, effectively rendering the mTLS authentication useless. The issue is that the Manager’s Certificate gRPC service does not validate if the requested IP addresses “belong to” the peer requesting the certificate—that is, if the peer connects from the same IP address as the one provided in the certificate request. This vulnerability is fixed in 2.1.0.
From the CVE record · GitHub_M
Before 2.1.0, Dragonfly’s Manager Certificate gRPC service does not verify that requested IP addresses belong to the requesting peer. A peer can obtain a valid TLS certificate for arbitrary IP addresses, effectively bypassing mTLS authentication.
Teams running dragonflyoss dragonfly or the Go packages github.com/dragonflyoss/dragonfly and d7y.io/dragonfly/v2 should check installations before 2.1.0.