Denial of service via unbounded resource allocation
Published May 11, 2021 · Updated Aug 3, 2024
Uncontrolled resource consumption in JetBrains IntelliJ IDEA before 2021.1 allows remote attackers to cause a denial of service. The product allocates resources without a published bound, but JetBrains has not identified the responsible component or attacker-controlled input. An unauthenticated remote path requires no user interaction, but public records do not distinguish a hang from a crash.
Summary
What happened
Uncontrolled resource consumption in JetBrains IntelliJ IDEA before 2021.1 allows remote attackers to cause a denial of service. The product allocates resources without a published bound, but JetBrains has not identified the responsible component or attacker-controlled input. An unauthenticated remote path requires no user interaction, but public records do not distinguish a hang from a crash.
The record
- CVE
- CVE-2021-30504
- Published
- May 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 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
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