Arcane: Container-registry credential exfiltration via URL repoint + test to attacker host
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to 2.5.0, UpdateRegistry and TestRegistry in backend/api/services/container_registry_service.go allow the registry URL to change while preserving the stored encrypted token. When a holder of registries:update and registries:test repoints a generic registry URL without supplying a replacement token, TestRegistry decrypts the preserved token and RegistryLogin sends it to the attacker-controlled host because normalizeRegistryServerAddressInternal does not restrict the destination. This exposes the stored container-registry PAT or password and can enable image access or tampering. This issue is fixed in version 2.5.0.
Text from CVE List
Affected versions 2
- arcaneaffected: < 2.5.0CVE List
- github.com/getarcaneapp/arcane/backend, go<= 2.4.0GitHub
References 4
- github.com/getarcaneapp/arcane/commit/fe31693634f48f295a7d77d091085b331cf9e915Fixvia CVE List
- github.com/getarcaneapp/arcane/releases/tag/backend/v2.5.0Fixvia CVE List
- github.com/getarcaneapp/arcane/security/advisories/GHSA-9pxc-cxp5-qp54Advisoryvia CVE List
- github.com/getarcaneapp/arcane/pull/3317Referencevia CVE List