CVE-2017-15702

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 3.1%, top 13% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 6%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Apache Qpid Broker-J 0.18 through 0.32, if the broker is configured with different authentication providers on different ports one of which is an HTTP port, then the broker can be tricked by a remote unauthenticated attacker connecting to the HTTP port into using an authentication provider that was configured on a different port. The attacker still needs valid credentials with the authentication provider on the spoofed port. This becomes an issue when the spoofed port has weaker authentication protection (e.g., anonymous access, default accounts) and is normally protected by firewall rules or similar which can be circumvented by this vulnerability. AMQP ports are not affected. Versions 6.0.0 and newer are not affected.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
92.7%
KEV
Not listed

Published

December 1, 2017

Last Modified

May 13, 2026

Advisory Details (4)

Auto-updated May 17, 2026
No patch confirmed yet.
generic

CVE-2017-15702 - Apache Qpid™

https://qpid.apache.org/cves/CVE-2017-15702.html
generic
https://lists.apache.org/thread.html/59d241e30db23b8b0af26bb273f789aa1f08515d3dc1a3868d3ba090%40%3Cdev.qpid.apache.org%3E
generic

[QPID-8039] [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong authentication provider - ASF Jira

https://issues.apache.org/jira/browse/QPID-8039
generic
http://www.securityfocus.com/bid/102040

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.qpid:qpid-broker0.18 ... 0.32 (8 versions)6.0.0—

Data Freshness Timeline

(refreshed 9× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-27 03:05 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-23 21:30 UTCEPSS rescore
  16. 2026-06-22 14:23 UTCEPSS rescore
  17. 2026-06-22 14:23 UTCEPSS rescore
  18. 2026-06-21 14:54 UTCEPSS rescore
  19. 2026-06-21 14:54 UTCEPSS rescore
  20. 2026-06-21 01:57 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-19 19:23 UTCEPSS rescore
  23. 2026-06-19 19:23 UTCEPSS rescore
  24. 2026-06-18 17:50 UTCEPSS rescore
  25. 2026-06-17 17:50 UTCEPSS rescore
Show 50 more
  1. 2026-06-16 17:50 UTCEPSS rescore
  2. 2026-06-15 17:45 UTCEPSS rescore
  3. 2026-06-14 23:14 UTCEPSS rescore
  4. 2026-06-14 23:14 UTCEPSS rescore
  5. 2026-06-13 22:57 UTCEPSS rescore
  6. 2026-06-12 23:09 UTCEPSS rescore
  7. 2026-06-11 13:57 UTCEPSS rescore
  8. 2026-06-10 22:15 UTCEPSS rescore
  9. 2026-06-08 14:14 UTCEPSS rescore
  10. 2026-06-07 15:22 UTCEPSS rescore
  11. 2026-06-07 15:22 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-06 13:45 UTCEPSS rescore
  14. 2026-06-05 22:44 UTCEPSS rescore
  15. 2026-06-04 13:10 UTCEPSS rescore
  16. 2026-06-04 13:10 UTCEPSS rescore
  17. 2026-06-02 20:11 UTCEPSS rescore
  18. 2026-06-02 20:11 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-06-01 13:49 UTCEPSS rescore
  21. 2026-05-31 22:28 UTCEPSS rescore
  22. 2026-05-31 00:14 UTCEPSS rescore
  23. 2026-05-29 13:41 UTCEPSS rescore
  24. 2026-05-28 13:42 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-27 13:38 UTCEPSS rescore
  27. 2026-05-27 13:38 UTCEPSS rescore
  28. 2026-05-26 13:42 UTCEPSS rescore
  29. 2026-05-26 13:42 UTCEPSS rescore
  30. 2026-05-26 07:17 UTCEPSS rescore
  31. 2026-05-26 07:17 UTCEPSS rescore
  32. 2026-05-23 00:10 UTCEG score recompute
  33. 2026-05-22 21:15 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 11:21 UTCEPSS rescore
  39. 2026-05-20 11:21 UTCEPSS rescore
  40. 2026-05-20 07:46 UTCEG score recompute
  41. 2026-05-20 03:45 UTCEG score recompute
  42. 2026-05-19 23:44 UTCEG score recompute
  43. 2026-05-19 19:43 UTCEG score recompute
  44. 2026-05-19 15:42 UTCEG score recompute
  45. 2026-05-19 11:40 UTCEG score recompute
  46. 2026-05-19 07:13 UTCEG score recompute
  47. 2026-05-19 03:13 UTCEG score recompute
  48. 2026-05-18 23:11 UTCEG score recompute
  49. 2026-05-18 21:30 UTCEPSS rescore
  50. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-15702?
CVE-2017-15702 is a critical vulnerability published on December 1, 2017. In Apache Qpid Broker-J 0.18 through 0.32, if the broker is configured with different authentication providers on different ports one of which is an HTTP port, then the broker can be tricked by a remote unauthenticated attacker connecting to the HTTP port into using an authentication provider that…
When was CVE-2017-15702 disclosed?
CVE-2017-15702 was first published in the National Vulnerability Database on December 1, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-15702 actively exploited?
CVE-2017-15702 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-15702?
CVE-2017-15702 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-15702?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-15702, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-15702

Explore →

Is Your Infrastructure Affected by CVE-2017-15702?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs