CVE-2020-36282
First published: Fri Mar 12 2021(Updated: )
JMS Client for RabbitMQ 1.x before 1.15.2 and 2.x before 2.2.0 is vulnerable to unsafe deserialization that can result in code execution via crafted StreamMessage data.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| RabbitMQ (Pivotal Software) | >=1.0.0<1.15.2 | |
| RabbitMQ (Pivotal Software) | >=2.0.0<2.2.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-36282?
CVE-2020-36282 is considered high severity due to its potential for code execution via unsafe deserialization.
How do I fix CVE-2020-36282?
To mitigate CVE-2020-36282, upgrade to RabbitMQ JMS Client version 1.15.2 or 2.2.0 or later.
What versions of RabbitMQ JMS Client are affected by CVE-2020-36282?
CVE-2020-36282 affects RabbitMQ JMS Client versions prior to 1.15.2 and 2.2.0.
What type of vulnerability is CVE-2020-36282?
CVE-2020-36282 is a vulnerability associated with unsafe deserialization leading to potential remote code execution.
Can I continue using RabbitMQ JMS Client if I am on an affected version of CVE-2020-36282?
If you are using an affected version of RabbitMQ JMS Client, you should upgrade immediately to avoid security risks.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/weakness
- agent/last-modified-date
- agent/severity
- agent/author
- agent/references
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/rabbitmq
- canonical/rabbitmq (pivotal software)
- version/rabbitmq (pivotal software)/1.0.0
- version/rabbitmq (pivotal software)/2.0.0