Deserialization of Untrusted Data Affecting qpid-java-example package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL10-QPIDJAVAEXAMPLE-12227805
- published29 Aug 2025
- disclosed2 Jul 2016
Introduced: 2 Jul 2016
CVE-2016-4974 (opens in a new tab)How to fix?
There is no fixed version for RHEL:10 qpid-java-example.
NVD Description
Note: Versions mentioned in the description apply only to the upstream qpid-java-example package and not the qpid-java-example package as distributed by RHEL.
See How to fix? for RHEL:10 relevant fixed versions and status.
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.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=1352481
- https://access.redhat.com/security/cve/CVE-2016-4974
- http://packetstormsecurity.com/files/137749/Apache-Qpid-Untrusted-Input-Deserialization.html
- http://qpid.apache.org/components/jms/security-0-x.html
- http://qpid.apache.org/components/jms/security.html
- http://www.securityfocus.com/archive/1/538813/100/0/threaded
- http://www.securityfocus.com/bid/91537
- http://www.securitytracker.com/id/1036239
- https://issues.apache.org/jira/browse/QPIDJMS-188