CVE-2020-11075 json
Shell Escape in Anchore Engine
published 6y ago modified 4mo ago also EUVD-2020-3443
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- anchore engine 0.7.1
- github.com/anchore/anchore-engine@e417869 commit
- github.com/anchore/anchore-engine#431 pull request
- github.com/anchore/anchore-engine/issues/430 advisory
Is CVE-2020-11075 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.84% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- anchore anchore-engine
Classification
- Weakness
-
- CWE-114 Process Control
References
-
github.com
/anchore/anchore-engine/pull/431
patch, third-party-advisory
-
github.com
/anchore/anchore-engine/commit/e41786901f097fd32104447a45864073105d37db
patch, third-party-advisory
-
github.com
/anchore/anchore-engine/issues/430
patch, third-party-advisory
-
github.com
/anchore/anchore-engine/security/advisories/GHSA-w4rm-w22x-h7m5
third-party-advisory
Sources
- CVE List CVE-2020-11075
- NVD CVE-2020-11075
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Improved package identification information.