cve.bz

CVE-2023-32684 linuxfoundation lima

2.5 lowEPSS 0.3%Fix available

Low (2.5) in linuxfoundation lima. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/lima-vm/lima 0.16.0.

On this page
Lima launches Linux virtual machines, typically on macOS, for running containerd. Prior to version 0.16.0, a virtual machine instance with a malicious disk image could read a single file on the host filesystem, even when no filesystem is mounted from the host. The official templates of Lima and the well-known third party products (Colima, Rancher Desktop, and Finch) are unlikely to be affected by this issue. To exploit this issue, the attacker has to embed the target file path (an absolute or a relative path from the instance directory) in a malicious disk image, as the qcow2 (or vmdk) backing file path string. As Lima refuses to run as the root, it is practically impossible for the attacker to read the entire host disk via `/dev/rdiskN`. Also, practically, the attacker cannot read at least the first 512 bytes (MBR) of the target file. The issue has been patched in Lima in version 0.16.0 by prohibiting using a backing file path in the VM base image.

Severity

CVSS 3.1

2.5 low
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 19th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-01-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-552 Files or Directories Accessible to External Parties
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-32684 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-32684?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-32684?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-32684 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:limabefore 0.16.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f7qw-jj9c-rpq9Gogithub.com/lima-vm/lima<0.16.00.16.0
GO-2023-1803Gogithub.com/lima-vm/lima<0.16.00.16.0

Attack patterns (CAPEC)

  • CAPEC-150 Collect Data from Common Resource Locations Severity: Medium
  • CAPEC-639 Probe System Files Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON