Quick answers
- Is CVE-2015-3188 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2015-3188 being exploited in the wild.
- How severe is CVE-2015-3188?
- Critical severity, with a CVSS score of 9.8, published 13 January 2017.
- Which products and versions are affected?
- org.apache.storm:storm (Maven) ECOSYSTEM:introduced=0.10.0-beta,fixed=0.10.0-beta1.
- Is there a fix for CVE-2015-3188?
- Yes. org.apache.storm:storm (Maven): upgrade to 0.10.0-beta1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2015-3188 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2015-3188?
- Check whether you run Apache Storm or org.apache.storm:storm (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.apache.storm:storm (Maven): upgrade to 0.10.0-beta1 or later
# set org.apache.storm:storm to 0.10.0-beta1 in your pom.xml or build.gradle
Technical details
A remote code execution (RCE) vulnerability exists in the UI daemon of Apache Storm version 0.10.0 prior to the 0.10.0-beta1 release. The flaw is rooted in improper permissions and access controls (CWE-264) within the web-based management interface. A network-based attacker can exploit this vulnerability without authentication or user interaction to execute arbitrary code on the host running the UI daemon. This allows for complete compromise of confidentiality, integrity, and availability. Users are advised to upgrade to version 0.10.0-beta1 or later to mitigate this risk.
Affected products
- Apache Storm 0.10.0 before 0.10.0-beta1
Identifiers
- CVE-2015-3188
- GHSA-cg5h-q983-4rww
Timeline
- 2015-06-23: disclosed: Initial public disclosure via security mailing lists
- 2017-01-13: advisory: NVD publication date