The Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression). All users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
Information
Published : 2021-10-19 08:15
Updated : 2023-02-24 09:00
NVD link : CVE-2021-37136
Mitre link : CVE-2021-37136
JSON object : View
CWE
CWE-400
Uncontrolled Resource Consumption
Products Affected
oracle
- webcenter_portal
- communications_cloud_native_core_unified_data_repository
- communications_cloud_native_core_security_edge_protection_proxy
- banking_apis
- communications_cloud_native_core_binding_support_function
- communications_instant_messaging_server
- coherence
- peoplesoft_enterprise_peopletools
- communications_cloud_native_core_policy
- communications_cloud_native_core_network_slice_selection_function
- banking_digital_experience
- helidon
- communications_brm_-_elastic_charging_engine
- commerce_guided_search
- communications_diameter_signaling_router
netty
- netty
netapp
- oncommand_insight
quarkus
- quarkus
debian
- debian_linux