# What is CVE-2018-17187? > CVE-2018-17187 is a high-severity flaw (CVSS 7.4) in Qpid Proton-J from Apache, published on 13 November 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 2.5%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2018-17187 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 46 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes. - **Severity:** High (CVSS 7.4 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 2.5% (latest exploit-likelihood forecast) - **Published:** 13 November 2018 - **Record last updated:** 31 January 2019 - **Main product:** Qpid Proton-J from Apache - **Affected products:** 1 ## What is CVE-2018-17187? In plain terms It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data and change data. ### The official description 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. ### What kind of flaw is it? - CWE-295: Improper Certificate Validation ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Hard: conditions must line up - Login needed first: No login needed - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can read data and change data Severity vector: `CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N` ## Is CVE-2018-17187 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.5%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 2.5%, 2.5%, 2.5%, 2.5%, 2.5%, 2.5%, 2.5%. ### Timeline - 13 November 2018: Published - 31 January 2019: Record last updated ### How Precursor Intelligence ranks it CVE-2018-17187 scores **46 out of 100 (Medium)**, with the action "Plan remediation". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2018-17187? The published record lists 1 product. - [Qpid Proton-J](https://www.precursorintelligence.com/product/apache/qpid_proton-j) by [Apache](https://www.precursorintelligence.com/vendors/apache) (Application): 0.3 to 0.29.0 ## How do I fix CVE-2018-17187? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [issues.apache.org](https://issues.apache.org/jira/browse/PROTON-1962) (Vendor advisory) - [mail-archives.apache.org](https://mail-archives.apache.org/mod_mbox/qpid-users/201811.mbox/%3CCAFitrpQSV73Vz7rJYfLJK7gvEymZSCR5ooWUeU8j4jzRydk-eg%40mail.gmail.com%3E) (Mitigation, Mailing list, Vendor advisory) - [qpid.apache.org](https://qpid.apache.org/cves/CVE-2018-17187.html) (Mitigation, Vendor advisory) - [securityfocus.com](http://www.securityfocus.com/bid/105935) (Third-party advisory, Vulnerability database) ## Questions ### What is CVE-2018-17187? CVE-2018-17187 is a high-severity flaw in Qpid Proton-J from Apache, published on 13 November 2018. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data and change data. ### How serious is CVE-2018-17187? It scores 7.4 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2018-17187 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2018-17187 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.5%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2018-17187 affect? For Qpid Proton-J from Apache: 0.3 to 0.29.0. ### How do I fix CVE-2018-17187? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2018-17187 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact