Skip to content
Fencer Intel
high 7.5

CVE-2016-4974 json

Improper Input Validation in Apache Qpid AMQP 0-x JMS

published 2016-07-13 10 y ago modified 2026-06-17 4 mo ago also GHSA-f38p-mq64-h784 , EUVD-2022-3674

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.2%
EPSS 6.2% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.qpid:qpid-jms-client 0.10.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-4974 updated cvss 5.6

qpid-java: Deserialization of untrusted input while using JMS ObjectMessage

  • Red Hat Enterprise MRG 2 qpid-java, qpid-java-client, qpid-java-common, qpid-java-example Red Hat Enterprise MRG 3 qpid-java
    affected: no fix planned “Will not fix”
  • Red Hat Satellite 6 qpid-java
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.25% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.0 AV:N/AC:M/Au:S/C:P/I:P/A:P
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.qpid:qpid-jms-client
<0.10.0
0.10.0

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.