Nx: Zip-Slip in the self-hosted remote cache
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 22.7.7, 23.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Nx is a monorepo solution for TypeScript and polyglot codebases. From version 20.8.0 until 22.7.7 and 23.0.2, the Nx self-hosted HTTP remote cache extracts downloaded cache artifacts without constraining where files are written. A malicious or on-path (MITM) remote cache server can return a crafted tar archive whose entries escape the cache directory and write to arbitrary locations on the machine running Nx, which can be escalated to remote code execution. Nx's default local cache and Nx Cloud are not affected; only workspaces configured to use a self-hosted remote cache are affected. This issue is fixed in versions 22.7.7 and 23.0.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- nrwl nx
From 20.8.0 · fixed in 22.7.7; From 23.0.0 · fixed in 23.0.2
- nxnpm
From 20.8.0 · fixed in 22.7.7
- @nx/s3-cachenpm
through 5.0.7
- @nx/gcs-cachenpm
through 5.0.7
- @nx/azure-cachenpm
through 5.0.7
- @nx/shared-fs-cachenpm
through 5.0.7
- @nx/powerpack-s3-cachenpm
through 5.0.7
- @nx/powerpack-gcs-cachenpm
through 5.0.7
- @nx/powerpack-azure-cachenpm
through 5.0.7
- @nx/powerpack-shared-fs-cachenpm
through 5.0.7
- nxnpm
From 23.0.0 · fixed in 23.0.2