dbcve.org
Qpid ProtonApplication · Apache

CVE-2016-4467

MEDIUM · 5.9 CVSS v3.0 Published 2017-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The C client and C-based client bindings in the Apache Qpid Proton library before 0.13.1 on Windows do not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate when using the SChannel-based security layer, which allows man-in-the-middle attackers to spoof servers via an arbitrary valid certificate.

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

The Apache Qpid Proton library's C client and C-based bindings on Windows fail to properly verify server hostname against the X.509 certificate's Common Name (CN) or subjectAltName fields when using SChannel-based security layer. This allows man-in-the-middle attackers to impersonate servers using any valid certificate.

MitigationUpgrade Apache Qpid Proton library to version 0.13.1 or later, which contains the proper hostname verification fix for SChannel connections.

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
Qpid ProtonApplication
Affected:= 0.8.0= 0.9.0= 0.9.1= 0.10.0= 0.11.0= 0.11.1= 0.12.0= 0.12.1= 0.12.2= 0.13.0

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
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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 installed Apache Qpid Proton version
    Check the version of the qpid-proton library or executable in your environment. On Windows, this may be in the installation directory or reported by the application using the library. Common locations include the system PATH or application-specific directories.
    Affected if The installed version is exactly 0.8.0, 0.9.0, 0.9.1, 0.10.0, 0.11.0, 0.11.1, 0.12.0, 0.12.1, 0.12.2, or 0.13.0.
  2. Confirm Windows platform
    Verify that the affected system is running Windows, as this vulnerability only applies to the SChannel-based security layer which is Windows-specific.
    Affected if The system is running Windows and uses the SChannel security layer for SSL/TLS connections.
  3. Check if SChannel security is in use
    Review your application or service configuration to determine if SChannel is being used for encrypted connections. This is typically the default SSL/TLS implementation on Windows for Proton-based applications.
    Affected if Connections are using SChannel for SSL/TLS and the Proton version is one of the affected versions listed.
  4. Verify hostname verification is disabled
    Inspect the SSL/TLS configuration or code that initializes the Proton connection. Look for settings related to hostname verification, peer verification, or certificate validation. On Windows with SChannel, check if the PN_SSL_VERIFY_PEER or similar flag is set to disable verification.
    Affected if Hostname verification is disabled or not properly implemented in the SChannel configuration for Proton connections.

You are affected if you are running Windows with Apache Qpid Proton versions 0.8.0 through 0.13.0 using SChannel-based SSL/TLS connections and hostname verification is not properly enforced.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache Qpid Proton library to version 0.13.1 or later, which contains the proper hostname verification fix for SChannel connections.

Fix this in Qpid Proton 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 help mitigating

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-2016-4467 — 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-2016-4467 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