CVE-2017-15702
moderate-risk
Published 2017-12-01
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.
Do I need to act?
~
3.1% chance of exploitation in next 30 days
EPSS score — moderate exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
9
CVSS 9.8/10
Critical
NETWORK
/ LOW complexity
Affected Products (1)
Qpid Broker-J
Affected Vendors
References (8)
Third Party Advisory
http://www.securityfocus.com/bid/102040
Vendor Advisory
https://issues.apache.org/jira/browse/QPID-8039
Vendor Advisory
https://qpid.apache.org/cves/CVE-2017-15702.html
Third Party Advisory
http://www.securityfocus.com/bid/102040
Vendor Advisory
https://issues.apache.org/jira/browse/QPID-8039
Vendor Advisory
https://qpid.apache.org/cves/CVE-2017-15702.html
43
/ 100
moderate-risk
Severity
32/34 · Critical
Exploitability
6/34 · Minimal
Exposure
5/34 · Minimal