Summary
Cache driver GetBlob() allows read access to any blob without access control check
Details
If a Zot accessControl policy allows users read access to some repositories but restricts read access to other repositories and dedupe is enabled (it is enabled by default), then an attacker who knows the name of an image and the digest of a blob (that they do not have read access to), they may maliciously read it via a second repository they do have read access to. This allows an attacker to read an image that the accessControl policy denies.
This attack is possible because ImageStore.CheckBlob() calls checkCacheBlob() to find the blob a global cache by searching for the digest. If it is found, it is copied to the user requested repository with copyBlob().
This cache behavior is intentionally used in RouteHandler.CreateBlobUpload() to implement cross repository blob mount (POST /v2/<name>/blobs/uploads/?mount=<digest>&from=<repository name>) in Zot. This is still missing an access control to check read access on the source repository.
This cache behavior is unexpectedly also used in RouteHandler.CheckBlob() too for HEAD /v2/<name>/blobs/<digest>. If a blob is requested that does not exist on the requested repository, Zot will search for it in a global cache (possibly returning a result from an from an incorrect repository) and then will store it into the ImageStore for the requested repository.
RouteHandler.GetBlob() does not call ImageStore.CheckBlob() so it is not directly vulnerable. However an attacker with only limited read access may first call CheckBlob() to fetch the blob from the cache, then call GetBlob() to read the blob.
Mitigation
The attack may be mitigated by configuring "dedupe": false in the "storage" settings. This disables Zot's cache drivers. dedupe is enabled by default using the BoltDB cache driver.
Impact
An attacker can read images that the accessControl policy denies if they have read access to any other second repository.
This attack only allows accessing blobs (both config and layers) by digest. Manifests cannot be accessed.
This attack requires the attacker to know the name of a private image and its layer digests. A scenario where this might happen is if a project has public CI build logs but publishes the image to a private repository. Many image build tools log layer digests.
Summary
Cache driver
GetBlob()allows read access to any blob without access control checkDetails
If a Zot
accessControlpolicy allows users read access to some repositories but restricts read access to other repositories anddedupeis enabled (it is enabled by default), then an attacker who knows the name of an image and the digest of a blob (that they do not have read access to), they may maliciously read it via a second repository they do have read access to. This allows an attacker to read an image that theaccessControlpolicy denies.This attack is possible because
ImageStore.CheckBlob()callscheckCacheBlob()to find the blob a global cache by searching for the digest. If it is found, it is copied to the user requested repository withcopyBlob().This cache behavior is intentionally used in
RouteHandler.CreateBlobUpload()to implement cross repository blob mount (POST /v2/<name>/blobs/uploads/?mount=<digest>&from=<repository name>) in Zot. This is still missing an access control to check read access on the source repository.This cache behavior is unexpectedly also used in
RouteHandler.CheckBlob()too forHEAD /v2/<name>/blobs/<digest>. If a blob is requested that does not exist on the requested repository, Zot will search for it in a global cache (possibly returning a result from an from an incorrect repository) and then will store it into theImageStorefor the requested repository.RouteHandler.GetBlob()does not callImageStore.CheckBlob()so it is not directly vulnerable. However an attacker with only limited read access may first callCheckBlob()to fetch the blob from the cache, then callGetBlob()to read the blob.Mitigation
The attack may be mitigated by configuring
"dedupe": falsein the"storage"settings. This disables Zot's cache drivers.dedupeis enabled by default using the BoltDB cache driver.Impact
An attacker can read images that the
accessControlpolicy denies if they have read access to any other second repository.This attack only allows accessing blobs (both config and layers) by digest. Manifests cannot be accessed.
This attack requires the attacker to know the name of a private image and its layer digests. A scenario where this might happen is if a project has public CI build logs but publishes the image to a private repository. Many image build tools log layer digests.