CVE-2016-4467: n/a vulnerability

CVE-2016-4467: The C client and C-based client bindings in the Apache Qpid Proton library before 0.13.1 on Windows do not...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 00:32 UTC (UTC+00:00)

Security readout for executives and security teams

Windows applications using affected Apache Qpid Proton C clients could trust the wrong server during encrypted connections. A valid certificate for any domain might be accepted, letting a network-positioned attacker impersonate the intended messaging server. Exposure is limited to Windows deployments using Apache Qpid Proton C client code or C-based bindings before 0.13.1 with SChannel-backed TLS. Non-Windows deployments and non-C clients are not identified as affected in the provided sources. Treat this as a targeted transport-security issue, not a broad internet-facing server emergency. Prioritize remediation where Windows messaging clients carry sensitive data or connect across untrusted networks. Mitigation focus: Upgrade Apache Qpid Proton C client components to 0.13.1 or later.; Check Apache Qpid Proton guidance for any platform-specific remediation details.; Prioritize Windows systems using SChannel-backed TLS with Qpid Proton C bindings..

Prepared: Jun 13, 2026, 05:01 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-4467 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: May 2, 2017, 14:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
[qpid-commits] 20190423 [qpid-site] branch asf-site updated: update site content for CVE-2019-0223CVE reference · mailing-list, x_refsource_MLIST

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.