You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2019/04/23 10:26:00 UTC

[jira] [Updated] (PROTON-2014) [CVE-2019-0223] TLS Man in the Middle Vulnerability

     [ https://issues.apache.org/jira/browse/PROTON-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell updated PROTON-2014:
-----------------------------------
    Affects Version/s: proton-0.9
                       proton-0.9.1
                       proton-0.10
                       proton-0.11.0
                       proton-0.11.1
                       proton-0.12.0
                       proton-0.12.1
                       proton-0.12.2
                       proton-0.13.0
                       proton-0.13.1
                       proton-0.14.0
                       proton-0.15.0
                       proton-0.16.0
                       proton-c-0.17.0
                       proton-c-0.18.0
                       proton-c-0.18.1
                       proton-c-0.19.0
                       proton-c-0.20.0
                       proton-c-0.21.0
                       proton-c-0.22.0
                       proton-c-0.23.0
                       proton-c-0.24.0
                       proton-c-0.25.0
                       proton-c-0.26.0
                       proton-c-0.27.0
             Priority: Critical  (was: Major)
          Description: 
The TLS support in Apache Qpid Proton 0.9 - 0.27.0 can under some
circumstances connect as a client to a TLS server that offers anonymous
ciphers irrespective of whether the client was configured to verify the
server's certificate or certificate against the hostname used to connect.

This means that an undetected man in the middle attack could be
constructed if an attacker can arrange to intercept TLS traffic.

Versions 0.9 - 0.27.0 are affected when using OpenSSL prior to 1.1.0. This
includes the Qpid Proton C library, and all language binding libraries using
it. Installations using the native Windows Schannel TLS implementation or
using OpenSSL 1.1.0 or later are not affected.

Note that this attack will not work if client certificate authentication is
in use as anonymous ciphers cannot be used in this case.

Resolution:
Anyone using an affected version with OpenSSL prior to 1.1.0 should upgrade
their installation to 0.27.1 or higher for fix to this vulnerability.

References:
[1] https://qpid.apache.org/cves/CVE-2019-0223.html.


================

_Original Jira details:_

_Title:_ [c] Example broker can silently use anonymous ciphers when misconfigured
_Description:_ The example broker does not check the return value from {color:#2e3436}pn_ssl_domain_set_credentials(){color} and if given a bad certificate will allow anonymous ciphers without even displaying an error message.

  was:The example broker does not check the return value from {color:#2e3436}pn_ssl_domain_set_credentials(){color} and if given a bad certificate will allow anonymous ciphers without even displaying an error message.

          Component/s: ruby-binding
                       python-binding
                       proton-c
                       php-binding
                       perl-binding
                       javascript-binding
                       go-binding
                       examples
                       cpp-binding
              Summary: [CVE-2019-0223] TLS Man in the Middle Vulnerability  (was: [c] Example broker can silently use anonymous ciphers when misconfigured)

> [CVE-2019-0223] TLS Man in the Middle Vulnerability
> ---------------------------------------------------
>
>                 Key: PROTON-2014
>                 URL: https://issues.apache.org/jira/browse/PROTON-2014
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: cpp-binding, examples, go-binding, javascript-binding, perl-binding, php-binding, proton-c, python-binding, ruby-binding
>    Affects Versions: proton-0.9, proton-0.9.1, proton-0.10, proton-0.11.0, proton-0.11.1, proton-0.12.0, proton-0.12.1, proton-0.12.2, proton-0.13.0, proton-0.13.1, proton-0.14.0, proton-0.15.0, proton-0.16.0, proton-c-0.17.0, proton-c-0.18.0, proton-c-0.18.1, proton-c-0.19.0, proton-c-0.20.0, proton-c-0.21.0, proton-c-0.22.0, proton-c-0.23.0, proton-c-0.24.0, proton-c-0.25.0, proton-c-0.26.0, proton-c-0.27.0
>            Reporter: Andrew Stitcher
>            Assignee: Andrew Stitcher
>            Priority: Critical
>             Fix For: proton-c-0.27.1
>
>
> The TLS support in Apache Qpid Proton 0.9 - 0.27.0 can under some
> circumstances connect as a client to a TLS server that offers anonymous
> ciphers irrespective of whether the client was configured to verify the
> server's certificate or certificate against the hostname used to connect.
> This means that an undetected man in the middle attack could be
> constructed if an attacker can arrange to intercept TLS traffic.
> Versions 0.9 - 0.27.0 are affected when using OpenSSL prior to 1.1.0. This
> includes the Qpid Proton C library, and all language binding libraries using
> it. Installations using the native Windows Schannel TLS implementation or
> using OpenSSL 1.1.0 or later are not affected.
> Note that this attack will not work if client certificate authentication is
> in use as anonymous ciphers cannot be used in this case.
> Resolution:
> Anyone using an affected version with OpenSSL prior to 1.1.0 should upgrade
> their installation to 0.27.1 or higher for fix to this vulnerability.
> References:
> [1] https://qpid.apache.org/cves/CVE-2019-0223.html.
> ================
> _Original Jira details:_
> _Title:_ [c] Example broker can silently use anonymous ciphers when misconfigured
> _Description:_ The example broker does not check the return value from {color:#2e3436}pn_ssl_domain_set_credentials(){color} and if given a bad certificate will allow anonymous ciphers without even displaying an error message.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org