Improper input validation in Apache Amqp 0-X Jms Client
CVE-2016-4974
Apache Qpid AMQP 0-x JMS client before 6.0.4 and JMS (AMQP 1.0) before 0.10.0 does not restrict the use of classes available on the classpath, which might allow remote authenticated users with permission to send messages to deserialize arbitrary objects and execute arbitrary code by leveraging a crafted serialized object in a JMS ObjectMessage that is handled by the getObject function.
Vulnerability class: Drupalgeddon 2 (CVE-2018-7600)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.062, 93.7th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (ARPSyndicate/cvemon, PalindromeLabs/Java-Deserialization-CVEs). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- www.securityfocus.com/bid/91537 (Third Party Advisory, VDB Entry, vdb-entry)
- 20160702 [SECURITY] CVE-2016-4974: Apache Qpid: deserialization of untrusted input while using JMS ObjectMessage (mailing-list)
- issues.apache.org/jira/browse/QPIDJMS-188 (Issue Tracking)
- www.securitytracker.com/id/1036239 (Third Party Advisory, VDB Entry, vdb-entry)
- qpid.apache.org/components/jms/security-0-x.html (Vendor Advisory)
- packetstormsecurity.com/files/137749/Apache-Qpid-Untrusted-Input-Deserializatio… (VDB Entry, Third Party Advisory)
- qpid.apache.org/components/jms/security.html (Vendor Advisory)