Source-code disclosure via local log insertion
Published Apr 4, 2023 · Updated Feb 11, 2025
Sensitive-data exposure in JetBrains PhpStorm before 2023.1 allows local users to read source code from the local idea.log file. The IDE writes source-code content into idea.log, but JetBrains has not published the code path or input condition that triggers the logging. A local account with low privileges is required; exposure is limited to source code that the affected IDE instance recorded in its log.
Summary
What happened
Sensitive-data exposure in JetBrains PhpStorm before 2023.1 allows local users to read source code from the local idea.log file. The IDE writes source-code content into idea.log, but JetBrains has not published the code path or input condition that triggers the logging. A local account with low privileges is required; exposure is limited to source code that the affected IDE instance recorded in its log.
The record
- CVE
- CVE-2022-48435
- Published
- Apr 4, 2023
- Updated
- Feb 11, 2025
- Vendor
- JetBrains
- Product
- PhpStorm
- Classifications
- CWE-532, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 4, 2023CVE publishedPublication date reported by the CVE source.
- Feb 11, 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=0 <2023.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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