dbcve.org
QpidApplication · Apache

CVE-2019-0223

HIGH · 7.4 CVSS v3.1 Published 2019-04-23
Fix available
A fix is available. Upgrade to after 0.27.0 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
While investigating bug PROTON-2014, we discovered that under some circumstances Apache Qpid Proton versions 0.9 to 0.27.0 (C library and its language bindings) can connect to a peer anonymously using TLS *even when configured to verify the peer certificate* while used with OpenSSL versions before 1.1.0. This means that an undetected man in the middle attack could be constructed if an attacker can arrange to intercept TLS traffic.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Qpid Proton versions 0.9 to 0.27.0 contains a TLS certificate verification bypass vulnerability when used with OpenSSL versions prior to 1.1.0. Even when configured to verify peer certificates, the library can silently fall back to anonymous TLS connections under certain conditions, allowing undetected MITM attacks.

MitigationUpgrade Apache Qpid Proton to version 0.27.1 or later, and ensure OpenSSL 1.1.0 or newer is in use. Verify that TLS connections are actually performing certificate verification through testing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
QpidApplication
Affected:>= 0.9, <= 0.27.0
Jboss Amq Clients 2Application
Affected:all versions
OpenstackApplication
Affected:= 13= 14
SatelliteApplication
Affected:= 6.3= 6.4= 6.5
Enterprise Linux DesktopOperating system
Affected:= 6.0= 7.0
Enterprise Linux EusOperating system
Affected:= 6.7= 7.2= 7.3= 7.4= 7.5= 7.6
Enterprise Linux ServerOperating system
Affected:= 6.0= 7.0
Enterprise Linux Server AusOperating system
Affected:= 5.9= 6.4= 6.5= 6.6= 7.2= 7.3= 7.4= 7.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Qpid Proton installation and version
    Run 'rpm -qa | grep -i qpid' or 'dpkg -l | grep -i proton' to list installed qpid packages. Alternatively, check for libraries like 'libqpid-proton*' in /usr/lib or /usr/lib64.
    Affected if Version is 0.9 through 0.27.0 (any patch version in this range)
  2. Determine OpenSSL version in use
    Run 'openssl version' to see the OpenSSL version, or check the OpenSSL library linked to the qpid-proton library with 'ldd /path/to/libqpid-proton.so | grep ssl' and then 'openssl version -a' for the linked version.
    Affected if OpenSSL version is earlier than 1.1.0 (for example, 1.0.x series)
  3. Verify if TLS/SSL is in use for Qpid connections
    Inspect application configuration files or logs for AMQP over SSL/TLS (amqps://) URLs, or check if the application sets SSL/TLS options when creating Proton connections. Look for 'ssl' or 'tls' in connection strings or configuration.
    Affected if The application uses TLS/SSL-encrypted AMQP connections (amqps://) with Qpid Proton
  4. Check if peer certificate verification is configured
    Review the application code or configuration that initializes the Qpid Proton SSL/TLS context. Look for flags like SSL_VERIFY_PEER or equivalent verification settings being enabled.
    Affected if Peer certificate verification is configured as enabled (the vulnerability bypasses this setting)

You are affected if Apache Qpid Proton versions 0.9-0.27.0 is in use together with OpenSSL versions prior to 1.1.0 on TLS-enabled connections, regardless of whether peer verification is configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.27.0
Interim mitigation

Upgrade Apache Qpid Proton to version 0.27.1 or later, and ensure OpenSSL 1.1.0 or newer is in use. Verify that TLS connections are actually performing certificate verification through testing.

Fix this in Qpid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0223 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data