Command-output disclosure via permissive temporary files
Published Jan 11, 2022 · Updated Aug 2, 2024
Improper privilege management in ShellJS before 0.8.5 allows local users to read command output or interrupt synchronous execution. The synchronous shell.exec() path creates parameter, stdout, and stderr temporary files without owner-only permissions, exposing output and allowing file pre-creation. A local low-privileged user sharing the host can read sensitive command output or pre-create the files so exec() crashes.
Summary
What happened
Improper privilege management in ShellJS before 0.8.5 allows local users to read command output or interrupt synchronous execution. The synchronous shell.exec() path creates parameter, stdout, and stderr temporary files without owner-only permissions, exposing output and allowing file pre-creation. A local low-privileged user sharing the host can read sensitive command output or pre-create the files so exec() crashes.
The record
- CVE
- CVE-2022-0144
- Published
- Jan 11, 2022
- Updated
- Aug 2, 2024
- Vendor
- ShellJS
- Product
- ShellJS
- Classifications
- CWE-269, T1005
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=unspecified <0.8.5
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.
Public exploit references
No public exploit references are available in this record.
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