CVE-2016-4974: Improper Input Validation in Apache Qpid AMQP 0-x JMS

Summary

14/05/2022
Yes i
High
7.5

CVE-2016-4974: Improper Input Validation in Apache Qpid AMQP 0-x JMS. Affects org.apache.qpid:qpid-jms-client versions < 0.10.0. Fixed in 0.10.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Qpid AMQP 0-x JMS client is a Java Message Service (JMS) client library that allows applications to communicate using the Advanced Message Queuing Protocol (AMQP). It provides a reliable and efficient way to exchange messages between distributed systems. The vulnerability affects versions before 6.0.4 and 0.10.0 of the client library. The library does not properly validate input, allowing remote authenticated users with message-sending permissions to deserialize arbitrary objects and execute arbitrary code. This vulnerability can be exploited by crafting a serialized object in a JMS ObjectMessage and handling it with the getObject function.

Vulnerability Detail

The vulnerability in Apache Qpid AMQP 0-x JMS client and JMS (AMQP 1.0) allows remote authenticated users to execute arbitrary code by leveraging a crafted serialized object in a JMS ObjectMessage. The library does not restrict the use of classes available on the classpath, enabling the deserialization of arbitrary objects. This can lead to remote code execution and potential compromise of the affected system. The vulnerability has a CVSS score of 7.5, indicating a high severity level.

How To Fix

Minimum fixed version

0.10.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to the secure versions mentioned above.

Conclusion

The vulnerability in Apache Qpid AMQP 0-x JMS client and JMS (AMQP 1.0) allows remote authenticated users to execute arbitrary code by exploiting the deserialization of arbitrary objects. To mitigate this risk, it is crucial to upgrade to the secure versions mentioned above. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.qpid:qpid-jms-client →

Share this vulnerability

FAQ

Apache Qpid AMQP 0-x JMS client is a Java library that enables applications to communicate using the Advanced Message Queuing Protocol (AMQP). It provides a reliable and efficient way to exchange messages between distributed systems.

The vulnerability allows remote authenticated users to execute arbitrary code by exploiting the deserialization of arbitrary objects. This can lead to remote code execution and potential compromise of the affected system.

To fix this vulnerability, it is recommended to upgrade to version 6.0.4 or later for Apache Qpid AMQP 0-x JMS client, and version 0.10.0 or later for JMS (AMQP 1.0). These versions include the necessary fixes to properly validate input and prevent the deserialization of arbitrary objects.

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to the secure versions mentioned above.

The CVSS score of this vulnerability is 7.5, indicating a high severity level.

How To Fix

Minimum fixed version

0.10.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback