CVE-2020-11075
Anchore Engine vulnerability
In Anchore Engine version 0.7.0, a specially crafted container image manifest, fetched from a registry, can be used to trigger a shell escape flaw in the anchore engine analyzer service during an image analysis process. The image analysis operation can only be executed by an authenticated user via a valid API request to anchore engine, or if an already added image that anchore is monitoring has its manifest altered to exploit the same flaw. A successful attack can be used to execute commands that run in the analyzer environment, with the same permissions as the user that anchore engine is run as - including access to the credentials that Engine uses to access its own database which have read-write ability, as well as access to the running engien analyzer service environment. By default Anchore Engine is released and deployed as a container where the user is non-root, but if users run Engine directly or explicitly set the user to 'root' then that level of access may be gained in the execution environment where Engine runs. This issue is fixed in version 0.7.1.
Affected products
Engine. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Anchore Engine runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/anchore/anchore-engine/commit/e41786901f097fd32104447a45864073105d37db · Patch
- github.com/anchore/anchore-engine/issues/430 · Patch
- github.com/anchore/anchore-engine/pull/431 · Patch
- github.com/anchore/anchore-engine/security/advisories/GHSA-w4rm-w22x-h7m5 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-11075
- cve.org/CVERecord?id=CVE-2020-11075
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.