Source-code disclosure via idea.log logging
Published Apr 3, 2025 · Updated Apr 3, 2025
Sensitive information exposure in JetBrains IntelliJ IDEA before 2024.3 or 2024.2.4 allows local users to read source code from idea.log. The IDE writes project source text into its local diagnostic log instead of excluding sensitive code from logging. A local low-privileged account must access the IDE user's log files; the published impact is limited to source-code confidentiality.
Summary
What happened
Sensitive information exposure in JetBrains IntelliJ IDEA before 2024.3 or 2024.2.4 allows local users to read source code from idea.log. The IDE writes project source text into its local diagnostic log instead of excluding sensitive code from logging. A local low-privileged account must access the IDE user's log files; the published impact is limited to source-code confidentiality.
The record
- CVE
- CVE-2025-32054
- Published
- Apr 3, 2025
- Updated
- Apr 3, 2025
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-532, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2025CVE publishedPublication date reported by the CVE source.
- Apr 3, 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 <2024.3, 2024.2.4
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