Source-code insertion via debug logging
Published Mar 18, 2021 · Updated Aug 3, 2024
Improper log-content handling in JetBrains PhpStorm before 2020.3 allows attackers to insert source code into debug logs via unspecified vectors. JetBrains has not published the affected logger, the event that captures source text, or the input path that reaches the log. The required access and configuration are undisclosed; the documented consequence is limited to source text appearing in debug logs.
Summary
What happened
Improper log-content handling in JetBrains PhpStorm before 2020.3 allows attackers to insert source code into debug logs via unspecified vectors. JetBrains has not published the affected logger, the event that captures source text, or the input path that reaches the log. The required access and configuration are undisclosed; the documented consequence is limited to source text appearing in debug logs.
The record
- CVE
- CVE-2021-25764
- Published
- Mar 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
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
No sourced classifications are available.
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