Sensitive-file exposure via missing workspace pack context
Published Jun 13, 2022 · Updated Apr 23, 2025
Information exposure in npm CLI 7.9.0 through versions before 8.11.0 allows remote attackers to read files unintentionally published from workspaces. The pack and publish commands omit the workspace root prefix and workspace paths when calling libnpmpack, so npm-packlist cannot apply root ignore rules. Exposure requires a maintainer to pack or publish a workspace containing material excluded only by a root-level ignore file.
Summary
What happened
Information exposure in npm CLI 7.9.0 through versions before 8.11.0 allows remote attackers to read files unintentionally published from workspaces. The pack and publish commands omit the workspace root prefix and workspace paths when calling libnpmpack, so npm-packlist cannot apply root ignore rules. Exposure requires a maintainer to pack or publish a workspace containing material excluded only by a root-level ignore file.
The record
- CVE
- CVE-2022-29244
- Published
- Jun 13, 2022
- Updated
- Apr 23, 2025
- Vendor
- npm
- Product
- npm CLI
- Classifications
- CWE-200, T1530
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.9.0 <7.9.0*
- Affected versionversion=8.11.0 <8.11.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory impact-check procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo