Local log disclosure via world-readable default modes
Published Jan 19, 2022 · Updated Apr 23, 2025
Incorrect default permissions in log4js-node before 6.4.0 allow local users to read log data through Unix file access. The file and dateFile configure functions left mode unset for streamroller's 0644 default, while fileSync explicitly used 0644 when no mode was configured. Exposure requires a Unix host, use of a file-based appender without an explicit mode, and logs containing sensitive data.
Summary
What happened
Incorrect default permissions in log4js-node before 6.4.0 allow local users to read log data through Unix file access. The file and dateFile configure functions left mode unset for streamroller's 0644 default, while fileSync explicitly used 0644 when no mode was configured. Exposure requires a Unix host, use of a file-based appender without an explicit mode, and logs containing sensitive data.
The record
- CVE
- CVE-2022-21704
- Published
- Jan 19, 2022
- Updated
- Apr 23, 2025
- Vendor
- log4js-node
- Product
- log4js-node
- Classifications
- CWE-276, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 19, 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=< 6.4.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.
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