Arcane
Arcane: Container-registry credential exfiltration via URL repoint + test to attacker host
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.5.0
Fixed in 2.5.0
Mitigation
Upgrade arcane to 2.5.0 or later.
References
- Vendor advisory github.com/getarcaneapp/arcane/security/adviso…
- Patch github.com/getarcaneapp/arcane/pull/3317
- Patch github.com/getarcaneapp/arcane/commit/fe316936…
1 more
- Release notes github.com/getarcaneapp/arcane/releases/tag/ba…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.