# What is CVE-2017-9000? > CVE-2017-9000 is a critical-severity flaw (CVSS 9.8) in Arubaos from HP, published on 6 August 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 5.1%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2017-9000 ## At a glance - **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. - **Precursor Intelligence risk score:** 54 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes. - **Severity:** Critical (CVSS 9.8 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 5.1% (latest exploit-likelihood forecast) - **Published:** 6 August 2018 - **Record last updated:** 18 October 2018 - **Main product:** Arubaos from HP - **Affected products:** 1 ## What is CVE-2017-9000? In plain terms It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline. ### The official description ArubaOS, all versions prior to 6.3.1.25, 6.4 prior to 6.4.4.16, 6.5.x prior to 6.5.1.9, 6.5.2, 6.5.3 prior to 6.5.3.3, 6.5.4 prior to 6.5.4.2, 8.x prior to 8.1.0.4 FIPS and non-FIPS versions of software are both affected equally is vulnerable to unauthenticated arbitrary file access. An unauthenticated user with network access to an Aruba mobility controller on TCP port 8080 or 8081 may be able to access arbitrary files stored on the mobility controller. Ports 8080 and 8081 are used for captive portal functionality and are listening, by default, on all IP interfaces of the mobility controller, including captive portal interfaces. The attacker could access files which could contain passwords, keys, and other sensitive information that could lead to full system compromise. ### What kind of flaw is it? - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: No login needed - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can read data, change data and take it offline Severity vector: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` ## Is CVE-2017-9000 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 5.1%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 5.1%, 5.1%, 5.1%, 5.1%, 5.1%, 5.1%, 5.1%. ### Timeline - 6 August 2018: Published - 18 October 2018: Record last updated ### How Precursor Intelligence ranks it CVE-2017-9000 scores **54 out of 100 (Medium)**, with the action "Plan remediation". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: key context - Real threat activity around it: key context 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2017-9000? The published record lists 1 product. Versions are as published: "before 6.3.1.25" means every version up to, but not including, 6.3.1.25. - [Arubaos](https://www.precursorintelligence.com/product/hp/arubaos) by [HP](https://www.precursorintelligence.com/vendors/hp) (Operating system): before 6.3.1.25, 6.4 to before 6.4.4.16, 6.5.0 to before 6.5.1.9, 6.5.2, 6.5.3 to before 6.5.3.3, 6.5.4 to before 6.5.4.2, 8.0 to before 8.1.0.4 ## How do I fix CVE-2017-9000? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [arubanetworks.com](http://www.arubanetworks.com/assets/alert/ARUBA-PSA-2017-006.txt) (Vendor advisory) - [securitytracker.com](http://www.securitytracker.com/id/1039580) (Third-party advisory, Vulnerability database) ## Questions ### What is CVE-2017-9000? CVE-2017-9000 is a critical-severity flaw in Arubaos from HP, published on 6 August 2018. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline. ### How serious is CVE-2017-9000? It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2017-9000 is 54 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. ### Is CVE-2017-9000 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 5.1%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2017-9000 affect? For Arubaos from HP: before 6.3.1.25, 6.4 to before 6.4.4.16, 6.5.0 to before 6.5.1.9, 6.5.2, 6.5.3 to before 6.5.3.3, 6.5.4 to before 6.5.4.2 and 1 more. ### How do I fix CVE-2017-9000? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2017-9000 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact