LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36282: JMS Client for RabbitMQ 1.x before 1.15.2 and 2.x before 2.2.0 is vulnerable to unsafe deserialization that...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-36282 affects RabbitMQ JMS Client versions before 1.15.2 in the 1.x line and before 2.2.0 in the 2.x line. Crafted StreamMessage data can trigger unsafe deserialization and potentially code execution. Treat this as serious where JMS messages may originate from untrusted or weakly controlled producers.

Executive priority

Prioritize remediation for systems where RabbitMQ JMS messages cross trust boundaries or support business-critical workflows. The impact is potentially code execution, but urgency should be based on confirmed use of affected client versions and exposure of message-producing paths.

Technical view

The CVE describes unsafe deserialization in JMS Client for RabbitMQ when handling crafted StreamMessage data. Affected ranges are 1.x before 1.15.2 and 2.x before 2.2.0. The supplied sources do not provide CVSS, CWE, exploit maturity, or detailed preconditions beyond crafted StreamMessage input.

Likely exposure

Exposure is likely limited to Java applications using RabbitMQ JMS Client in the affected version ranges and processing StreamMessage payloads. Risk increases when message producers, queues, or broker access are externally reachable, shared across tenants, or not strongly authenticated.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The public description states code execution may occur via crafted StreamMessage data, but the supplied evidence does not establish real-world exploitation, exploit availability, or required attacker access level.

Researcher notes

Key gaps remain: no CVSS vector, CWE assignment, proof of exploitation, or detailed fix mechanics are included in the bundle. Analysis should stay anchored to the affected version ranges, unsafe deserialization condition, and crafted StreamMessage trigger described by the CVE sources.

Mitigation direction

  • Upgrade 1.x deployments to RabbitMQ JMS Client 1.15.2 or later.
  • Upgrade 2.x deployments to RabbitMQ JMS Client 2.2.0 or later.
  • Review the linked RabbitMQ issue and release notes for vendor-specific guidance.
  • Restrict JMS producer access to trusted authenticated systems.
  • Audit queues carrying StreamMessage data for untrusted sources.

Validation and detection

  • Inventory Java dependencies for rabbitmq-jms-client versions.
  • Confirm no deployed application uses 1.x before 1.15.2.
  • Confirm no deployed application uses 2.x before 2.2.0.
  • Map which services consume StreamMessage payloads through RabbitMQ JMS.
  • Verify broker and queue permissions limit message producers.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-36282 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.