Information disclosure via unrestricted debugger-port binding
Published Apr 28, 2022 · Updated Aug 3, 2024
Information disclosure in JetBrains PyCharm before 2022.1 allows attackers on the internal network to access debugger data. The debugger listener binds to an unrestricted network interface instead of loopback, exposing its port to other internal hosts. A local user must start and interact with a debugging session; the documented consequence is limited to data disclosure.
Summary
What happened
Information disclosure in JetBrains PyCharm before 2022.1 allows attackers on the internal network to access debugger data. The debugger listener binds to an unrestricted network interface instead of loopback, exposing its port to other internal hosts. A local user must start and interact with a debugging session; the documented consequence is limited to data disclosure.
The record
- CVE
- CVE-2022-29820
- Published
- Apr 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- JetBrains
- Product
- PyCharm
- Classifications
- CWE-668, CWE-1327
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 28, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2022.1 <2022.1
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.
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