Local information disclosure via world-readable logfiles
Published Jan 13, 2023 · Updated Nov 4, 2025
Information disclosure in Eternal Terminal 6.2.1 allows local users to read etclient and etserver stdout logs stored in /tmp. The etclient and etserver logging path creates stdout files with mode 0644, granting every local account read access. Local filesystem access is required, and exposure is limited to data written into those logs by the affected client or server.
Summary
What happened
Information disclosure in Eternal Terminal 6.2.1 allows local users to read etclient and etserver stdout logs stored in /tmp. The etclient and etserver logging path creates stdout files with mode 0644, granting every local account read access. Local filesystem access is required, and exposure is limited to data written into those logs by the affected client or server.
The record
- CVE
- CVE-2022-48258
- Published
- Jan 13, 2023
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
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