LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Portainer 1.24.1 and earlier allowed a restriction to be enforced only in the browser, not on the server. If abused, an attacker with enough access to create a container could use bind mounts to reach beyond the container and potentially take over the Docker host.

Executive priority

Prioritize any affected internet-facing or broadly reachable Portainer deployment. The business impact could be full compromise of Docker hosts, but current evidence does not prove active exploitation.

Technical view

The reported flaw is incorrect access control around bind mount restrictions. Server-side enforcement was missing, so client-side checks could be bypassed to spawn a container with a bind mount. The source states this could enable container escape and complete Docker host takeover.

Likely exposure

Exposure is most relevant to organizations running Portainer 1.24.1 or earlier on Docker hosts. The bundle does not clearly state authentication prerequisites, so treat reachable Portainer instances with container-management access as the main risk.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. It does describe a plausible remote code execution path ending in Docker host takeover, but provides limited operational detail and no CVSS score.

Researcher notes

Metadata is incomplete: severity, CVSS, CWE, CPEs, and explicit fixed version are absent in the supplied bundle. Analysis should stay tied to Portainer 1.24.1 and earlier and the GitHub issue referenced by CVE.

Mitigation direction

  • Identify any Portainer instances running 1.24.1 or earlier.
  • Check Portainer vendor guidance for fixed versions or supported remediation.
  • Restrict Portainer access to trusted administrators only.
  • Limit network exposure to Portainer management interfaces.
  • Review Docker host access controls and container creation permissions.

Validation and detection

  • Inventory Portainer versions across Docker management environments.
  • Confirm whether affected instances are reachable from untrusted networks.
  • Review Portainer users and roles with container creation capability.
  • Look for unexpected containers using sensitive bind mounts.
  • Check Docker host logs for suspicious container creation activity.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-24264 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.