zot create-only policy allows overwrite attempts of existing latest tag (update permission not required)
project-zot zot
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| zotregistry.dev/zot/v2 Go |
|
|
| zotregistry.dev/zot Go |
| No fix yet |
project-zot zot
| Product | Affected | Fixed in |
|---|---|---|
| zotregistry.dev/zot/v2 Go |
|
|
| zotregistry.dev/zot Go |
| No fix yet |
zot is ancontainer image/artifact registry based on the Open Container Initiative Distribution Specification. From 1.3.0 to 2.1.14, zot’s dist-spec authorization middleware infers the required action for PUT /v2/{name}/manifests/{reference} as create by default, and only switches to update when the tag already exists and reference != "latest". As a result, when latest already exists, a user who is allowed to create (but not allowed to update) can still pass the authorization check for an overwrite attempt of latest. This vulnerability is fixed in 2.1.15.
From the CVE record · GitHub_M
zot’s dist-spec authorization middleware can treat an attempt to overwrite the existing `latest` tag as a create action. An authenticated user allowed to create but not update can therefore pass the authorization check for that overwrite attempt. The input does not specify any required user interaction.
Operators using Go package `zotregistry.dev/zot/v2` before 2.1.15 or `zotregistry.dev/zot` from 1.3.0-20210831063041-c8779d9e87d9 through 1.4.4-20251014054906-73eef25681af should check their deployments.