Remote code execution via unsafe client deserialization
Published Jan 28, 2021 · Updated Sep 16, 2024
Unsafe deserialization in IBM MQ Java and JMS client libraries 7.5 through 9.2 allows remote attackers to execute arbitrary code. The libraries unsafely deserialize trusted data; IBM has not published the entry point, accepted object types, or gadget path. Network access requires no authentication, but IBM rates exploitation as high complexity; successful exploitation executes code on the affected system.
Summary
What happened
Unsafe deserialization in IBM MQ Java and JMS client libraries 7.5 through 9.2 allows remote attackers to execute arbitrary code. The libraries unsafely deserialize trusted data; IBM has not published the entry point, accepted object types, or gadget path. Network access requires no authentication, but IBM rates exploitation as high complexity; successful exploitation executes code on the affected system.
The record
- CVE
- CVE-2020-4682
- Published
- Jan 28, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM MQ
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=7.5.0
- Affected versionversion=8.0.0
- Affected versionversion=9.0.0
- Affected versionversion=9.1.0
- Affected versionversion=9.2.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