high CVSS 7.2 EPSS 0.49%

CVE-2024-2240·Docker vulnerability

Docker daemon in Brocade SANnav before SANnav 2.3.1b runs without auditing. The vulnerability could allow a remote authenticated attacker to execute various attacks.

Severity
high
Software
Docker
Fixed in
2.3.1b
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.49% — higher than 40% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2024-2240 scores 7.2 on CVSS, so a successful attack would be serious — but at 0.49%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

Until: 2.3.1b

Fixed in: 2.3.1b

How to fix this CVE

Update Docker to version 2.3.1b or later to restore audit logging capabilities and prevent unauthorized remote access by authenticated attackers. The vulnerability stems from disabled audit trails in the Docker daemon, which could allow attackers to perform sensitive operations without detection. Prioritize this update for any systems running Brocade SANnav environments or Docker instances that require compliance and security monitoring.

sudo dnf update docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Run `docker --version` to retrieve the installed Docker version and compare against 2.3.1b
  2. Check if audit logging is enabled by examining Docker daemon configuration: `cat /etc/docker/daemon.json | grep -i audit` — a missing or disabled audit setting indicates vulnerability
  3. Review Docker daemon logs for unauthorized container operations: `journalctl -u docker -n 500 | grep -iE '(exec|run|create|start)' | head -20`
  4. Verify the patch was applied by confirming Docker version is 2.3.1b or higher: `docker --version` should display version 2.3.1b or later

FAQ

What is CVE-2024-2240?

CVE-2024-2240 is a high-severity vulnerability in Docker daemon running within Brocade SANnav environments where audit logging is disabled, allowing authenticated remote attackers to execute operations without creating audit trails.

Is CVE-2024-2240 being actively exploited?

No, CVE-2024-2240 is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available at this time.

What versions of Docker are affected by CVE-2024-2240?

All versions of Docker in Brocade SANnav prior to version 2.3.1b are affected. The vulnerability is fixed in SANnav 2.3.1b and later releases.

How do I check if my server is vulnerable to CVE-2024-2240?

Run `docker --version` and confirm the version is below 2.3.1b, then check if audit logging is disabled in `/etc/docker/daemon.json` using `cat /etc/docker/daemon.json | grep -i audit`.

Does Defensia detect CVE-2024-2240?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2024-2240 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-42298CVSS 10Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUB_TOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.
CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
CVE-2026-44182CVSS 10Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions prior to 3.3.0, the server interpolates untrusted environment variables (e.g., KERNEL_XXX) into Kubernetes manifests without YAML-aware escaping, enabling YAML injection attacks. Attackers can inject new fields, overwrite critical fields (e.g., duplicate securityContext keys, where the last one prevails), and inject document boundaries (--- for new documents, ... for end-of-document) to generate multiple resources, potentially creating arbitrary types, such as privileged pods. The Jinja2 template for the Kubernetes manifest contains several kernel_xxx variables, such as kernel_working_dir that are used when rendering the manifest and are all vectors for YAML injection. This issue has been fixed in version 3.3.0.
CVE-2026-44181CVSS 10Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions 2.0.0rc2 and above, prior to 3.3.0, the environment variables (KERNEL_XXX) used during the rendering of the Kubernetes manifest are vulnerable to Server Side Template Injection (SSTI). By including Jinja2 template expressions it is possible to execution Python code and OS Commands in the Enterprise Gateway service. The code can use or steal the Kubernetes service account token, which can steal Kubernetes secrets and be used to fully compromise the Kubernetes cluster by scheduling a privileged pod or a pod with a hostPath volume mount. This issue has been fixed in version 3.3.0.
CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-2240. Free for 1 server.

Get started free