Remote code execution via RabbitMQ message deserialization
Published May 14, 2020 · Updated Aug 4, 2024
Deserialization of untrusted data in Apache Camel RabbitMQ 2.22.x through 2.25.0 and 3.0.0 through 3.1.0 allows remote attackers to execute code. RabbitMQMessageConverter.populateMessageBody invokes deserializeBody when a message carries the CamelSerialize header because serialization is enabled by default. Exploitation requires access to publish to a consumed RabbitMQ destination and a usable gadget on the application classpath; code runs in the Camel process.
Summary
What happened
Deserialization of untrusted data in Apache Camel RabbitMQ 2.22.x through 2.25.0 and 3.0.0 through 3.1.0 allows remote attackers to execute code. RabbitMQMessageConverter.populateMessageBody invokes deserializeBody when a message carries the CamelSerialize header because serialization is enabled by default. Exploitation requires access to publish to a consumed RabbitMQ destination and a usable gadget on the application classpath; code runs in the Camel process.
The record
- CVE
- CVE-2020-11972
- Published
- May 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Camel
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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