CVE-2017-15702
Last modified
CVE-2017-15702 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 6.21% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Qpid Broker-J | >= 0.18, <= 0.32 |
References
- http://www.securityfocus.com/bid/102040Third Party Advisory, VDB Entry
- https://issues.apache.org/jira/browse/QPID-8039Vendor Advisory
- https://qpid.apache.org/cves/CVE-2017-15702.htmlVendor Advisory
- http://www.securityfocus.com/bid/102040Third Party Advisory, VDB Entry
- https://issues.apache.org/jira/browse/QPID-8039Vendor Advisory
- https://qpid.apache.org/cves/CVE-2017-15702.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-15702?
How severe is CVE-2017-15702?
How do I fix CVE-2017-15702?
Are you affected by CVE-2017-15702?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
