CVE-2019-0223

NameCVE-2019-0223
DescriptionWhile 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.
SourceCVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)
NVD severitymedium

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
qpid-proton (PTS)stretch0.14.0-5vulnerable
buster0.22.0-3fixed
bullseye, sid0.22.0-3.3fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
qpid-protonsource(unstable)0.22.0-1

Notes

[stretch] - qpid-proton <no-dsa> (Minor issue)
[jessie] - qpid-proton <ignored> (Minor issue)
https://issues.apache.org/jira/browse/PROTON-2014
https://qpid.apache.org/cves/CVE-2019-0223.html
https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=97c7733
https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=159fac1
https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=4aea0fd
https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=2d3ba8a
Source-wise only fixed in 0.27.1 upstream, but 0.22.0-1 upload in
unstable switched to build against OpenSSL 1.1 adressing the issue.
The description tells that the vulnerability was introduced in 0.9 but the
version in jessie (0.7) seems to be vulnerable too even though one file is
not present in the jessie version. That part do not seem to be essential for
the package to be vulnerable.

Search for package or bug name: Reporting problems