VulertSecurity VulertSecurity

CVE-2019-0200: Improper Input Validation in Apache Qpid Broker-J

org.apache.qpid:apache-qpid-broker-j Updated 02 Oct 2025

Summary

07/03/2019
CVE-2019-0200
Yes i
High
7.5

CVE-2019-0200: Improper Input Validation in Apache Qpid Broker-J. Affects org.apache.qpid:apache-qpid-broker-j across 2 version ranges.

< 7.0.7 >= 7.1.0, < 7.1.1

Fixed in 7.0.7 or 7.1.1, depending on the release line you run. 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.

A free account is created for continuous monitoring. By scanning, you agree to our Terms & Conditions.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache Qpid Broker-J is an open-source messaging broker that implements the Advanced Message Queuing Protocol (AMQP). It provides reliable messaging and supports various AMQP protocol versions. The vulnerability affects versions 6.0.0-7.0.6 and 7.1.0 of Apache Qpid Broker-J when using AMQP protocol versions below 1.0 (AMQP 0-8, 0-9, 0-91, and 0-10).

Vulnerability Detail

The vulnerability is an improper input validation issue that allows an unauthenticated attacker to crash the broker instance by sending specially crafted commands using the affected AMQP protocol versions. This can lead to a denial of service (DoS) condition. The vulnerability has a CVSS score of 7.5, indicating a high severity level. It was first published on March 7, 2019.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 7.0.7 7.0.7
  • >= 7.1.0, < 7.1.1 7.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Conclusion

The vulnerability in Apache Qpid Broker-J versions 6.0.0-7.0.6 and 7.1.0 can be mitigated by upgrading to versions 7.0.7 or 7.1.1 or later. It is important to promptly apply the necessary updates to prevent potential denial of service attacks. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for org.apache.qpid:apache-qpid-broker-j →

Share this vulnerability

FAQ

What is Apache Qpid Broker-J?

Apache Qpid Broker-J is an open-source messaging broker that implements the Advanced Message Queuing Protocol (AMQP). It provides reliable messaging and supports various AMQP protocol versions.

Versions 6.0.0-7.0.6 (inclusive) and 7.1.0 of Apache Qpid Broker-J are affected when using AMQP protocol versions 0-8, 0-9, 0-91, and 0-10.

The vulnerability allows an unauthenticated attacker to crash the broker instance, leading to a denial of service (DoS) condition.

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

To fix the vulnerability, upgrade to Qpid Broker-J versions 7.0.7 or 7.1.1 or later.

References

View More

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.qpid:apache-qpid-broker-j.

View all org.apache.qpid:apache-qpid-broker-j vulnerabilities →
Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 7.0.7 7.0.7
  • >= 7.1.0, < 7.1.1 7.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. 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