ubuntu-cve-2018-17187
Vulnerability from osv_ubuntu
Published
2018-11-13 15:29
Modified
2026-04-22 07:38
Summary
Details

The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the 'transport.ssl(...)' methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.

Severity
7.4 (High)
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
N/A (UNKNOWN)
medium
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libqpid-proton2",
            "binary_version": "0.10-2"
          },
          {
            "binary_name": "libqpid-proton2-dev-examples",
            "binary_version": "0.10-2"
          },
          {
            "binary_name": "python-qpid-proton",
            "binary_version": "0.10-2"
          },
          {
            "binary_name": "python3-qpid-proton",
            "binary_version": "0.10-2"
          },
          {
            "binary_name": "qpid-proton-dump",
            "binary_version": "0.10-2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:16.04:LTS",
        "name": "qpid-proton",
        "purl": "pkg:deb/ubuntu/qpid-proton@0.10-2?arch=source\u0026distro=xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.7-2",
        "0.10-2"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libqpid-proton-cpp8",
            "binary_version": "0.14.0-5.1ubuntu1"
          },
          {
            "binary_name": "libqpid-proton8",
            "binary_version": "0.14.0-5.1ubuntu1"
          },
          {
            "binary_name": "libqpid-proton8-dev-examples",
            "binary_version": "0.14.0-5.1ubuntu1"
          },
          {
            "binary_name": "python-qpid-proton",
            "binary_version": "0.14.0-5.1ubuntu1"
          },
          {
            "binary_name": "python3-qpid-proton",
            "binary_version": "0.14.0-5.1ubuntu1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "qpid-proton",
        "purl": "pkg:deb/ubuntu/qpid-proton@0.14.0-5.1ubuntu1?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.14.0-5.1",
        "0.14.0-5.1ubuntu1"
      ]
    }
  ],
  "aliases": [],
  "details": "The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the \u0027transport.ssl(...)\u0027 methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.",
  "id": "UBUNTU-CVE-2018-17187",
  "modified": "2026-04-22T07:38:44Z",
  "published": "2018-11-13T15:29:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2018-17187"
    },
    {
      "type": "REPORT",
      "url": "https://qpid.apache.org/cves/CVE-2018-17187.html"
    },
    {
      "type": "REPORT",
      "url": "https://issues.apache.org/jira/browse/PROTON-1962"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/apache/qpid-proton-j/commit/0cb8ca03cec42120dcfc434561592d89a89a805e"
    },
    {
      "type": "REPORT",
      "url": "https://mail-archives.apache.org/mod_mbox/qpid-users/201811.mbox/%3CCAFitrpQSV73Vz7rJYfLJK7gvEymZSCR5ooWUeU8j4jzRydk-eg%40mail.gmail.com%3E"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2018-17187"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "medium",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2018-17187"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.