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)
|
History
No history.
Information
Published : 2021-10-19 15:15
Updated : 2023-11-07 03:36
NVD link : CVE-2021-37136
Mitre link : CVE-2021-37136
CVE.ORG link : CVE-2021-37136
JSON object : View
Products Affected
oracle
- communications_cloud_native_core_network_slice_selection_function
- communications_cloud_native_core_unified_data_repository
- communications_cloud_native_core_security_edge_protection_proxy
- communications_cloud_native_core_policy
- webcenter_portal
- banking_apis
- banking_digital_experience
- communications_diameter_signaling_router
- communications_instant_messaging_server
- coherence
- helidon
- commerce_guided_search
- communications_brm_-_elastic_charging_engine
- communications_cloud_native_core_binding_support_function
- peoplesoft_enterprise_peopletools
debian
- debian_linux
quarkus
- quarkus
netapp
- oncommand_insight
netty
- netty
CWE
CWE-400
Uncontrolled Resource Consumption