Vulnerabilities · 2017 · Apache
CVE-2017-15702
Apache Qpid Broker-j vulnerability
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Qpid Broker-j. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Apache Qpid Broker-j runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- issues.apache.org/jira/browse/QPID-8039 · Vendor Advisory
- qpid.apache.org/cves/CVE-2017-15702.html · Vendor Advisory
- www.securityfocus.com/bid/102040 · Third Party Advisory
- lists.apache.org/thread.html/59d241e30db23b8b0af26bb273f789aa1f08515d3dc1a3868d3ba090%40%3
- nvd.nist.gov/vuln/detail/CVE-2017-15702
- cve.org/CVERecord?id=CVE-2017-15702
More vulnerabilities in Apache products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.