Skip to content

← Public intelligence

Go package

github.com/lima-vm/lima

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 2.7GoPublished

    In Lima, a malicious disk image could read a single file on the host filesystem as a qcow2/vmdk backing file

    CVE-2023-32684 · GHSA-f7qw-jj9c-rpq9

    Affected
    • Go github.com/lima-vm/lima < 0.16.0
    Fixed in
    0.16.0· Vendor fix available
    Issue
    Note 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. Impact 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. 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. Patches Patched in Lima v0.16.0, by prohibiting using a backing file path in the VM base image. Workarounds Do not use an untrusted disk image.

    Recommended action: Upgrade to 0.16.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →