Crabbox before 0.9.0 contains a path traversal vulnerability in the Islo provider's workspace path resolution that allows attackers to supply absolute or relative paths that resolve outside the intended /workspace directory. Attackers can craft a malicious .crabbox.yaml or crabbox.yaml file with traversal sequences to cause arbitrary file deletion and overwrite when sync.delete is enabled, as the workspace preparation logic executes rm -rf and mkdir -p operations on the resolved path without proper validation.
Security readout for executives and security teams
Plain-English summary
Crabbox before 0.9.0 can be tricked by a malicious project configuration into operating outside its intended workspace. If someone runs Crabbox against that configuration, workspace setup may delete or overwrite files on the local system. This is mainly a risk for developers or automation processing untrusted repositories or configs.
Executive priority
Treat this as a high-priority developer tooling issue. It can cause destructive local file changes when unsafe configuration is processed, but current evidence does not indicate internet-scale exploitation or KEV-listed active abuse.
Technical view
The Islo provider improperly validates workspace path resolution. Absolute paths or relative traversal in .crabbox.yaml/crabbox.yaml can resolve outside /workspace. When sync.delete is enabled, preparation logic performs destructive filesystem operations on that resolved path, creating integrity and availability impact. CVSS 3.1 is 7.1; CWE-22.
Likely exposure
Exposure is most likely where Crabbox versions before 0.9.0 are installed and used with the Islo provider, especially in developer machines, CI jobs, or automation that consumes external Crabbox configuration. The CVE requires local execution and user interaction, but no attacker privileges.
Exploitation context
The bundle does not show KEV listing or public active exploitation. Exploitation depends on convincing a user or workflow to process a malicious Crabbox configuration and having sync.delete enabled. Sources describe arbitrary deletion and overwrite potential, not remote unauthenticated compromise.
Researcher notes
Focus review on workspace path canonicalization, absolute path handling, traversal rejection, and destructive filesystem calls during workspace preparation. The source bundle names the 0.9.0 release and commit 6b07193fb5670aac315ea47215651c67b8127868 as the fix references.
Mitigation direction
Upgrade Crabbox to version 0.9.0 or later.
Avoid running Crabbox against untrusted repositories or configuration files.
Disable sync.delete where operationally possible until upgraded.
Review vendor release notes and patch references for exact fixed behavior.
Validation and detection
Inventory installed Crabbox versions on developer systems and CI workers.
Identify workflows using the Islo provider and sync.delete.
Check repositories for committed .crabbox.yaml or crabbox.yaml files from untrusted sources.
Confirm upgraded environments report Crabbox 0.9.0 or later.
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.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.