# What is CVE-2014-7231? > CVE-2014-7231 is a low-severity flaw (CVSS 2.1) in Cinder from Openstack, published on 8 October 2014. 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 0.5%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2014-7231 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 30 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes. - **Severity:** Low (CVSS 2.1 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:** 0.5% (latest exploit-likelihood forecast) - **Published:** 8 October 2014 - **Record last updated:** 12 April 2025 - **Main product:** Cinder from Openstack - **Affected products:** 4 ## What is CVE-2014-7231? In plain terms An attacker has to be already on the device without logging in. If it works, the attacker can read some data. ### The official description The strutils.mask_password function in the OpenStack Oslo utility library, Cinder, Nova, and Trove before 2013.2.4 and 2014.1 before 2014.1.3 does not properly mask passwords when logging commands, which allows local users to obtain passwords by reading the log. ### 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: Already on the device - How hard it is to pull off: Easy: no special conditions - Login needed first: No login needed - What an attacker gets: Can read some data Severity vector: `AV:L/AC:L/Au:N/C:P/I:N/A:N` ## Is CVE-2014-7231 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 0.5%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.5%, 0.5%, 0.5%, 0.5%, 0.5%, 0.5%, 0.5%. ### Timeline - 8 October 2014: Published - 12 April 2025: Record last updated ### How Precursor Intelligence ranks it CVE-2014-7231 scores **30 out of 100 (Low)**, with the action "Monitor". 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: smaller factor - Threat activity around it: smaller factor 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-2014-7231? The published record lists 4 products. Versions are as published: "2013.2 to before 2013.2.4" means from 2013.2 up to, but not including, 2013.2.4. - [Cinder](https://www.precursorintelligence.com/product/openstack/cinder) by [Openstack](https://www.precursorintelligence.com/vendors/openstack) (Application): 2013.2 to before 2013.2.4, 2014.1 to before 2014.1.3 - [Nova](https://www.precursorintelligence.com/product/openstack/nova) by [Openstack](https://www.precursorintelligence.com/vendors/openstack) (Application): 2013.2 to before 2013.2.4, 2014.1 to before 2014.1.3 - [Trove](https://www.precursorintelligence.com/product/openstack/trove) by [Openstack](https://www.precursorintelligence.com/vendors/openstack) (Application): 2013.2 to before 2013.2.4, 2014.1 to before 2014.1.3 - [Openstack](https://www.precursorintelligence.com/product/redhat/openstack) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Application): 5.0 ## How do I fix CVE-2014-7231? 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 latest update from the vendor. The references list where the vendor has published details. 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 - [rhn.redhat.com](http://rhn.redhat.com/errata/RHSA-2014-1939.html) (Third-party advisory) - [seclists.org](http://seclists.org/oss-sec/2014/q3/853) (Mailing list, Third-party advisory) - [securityfocus.com](http://www.securityfocus.com/bid/70184) (Third-party advisory, Vulnerability database) - [bugs.launchpad.net](https://bugs.launchpad.net/oslo.utils/+bug/1345233) (Exploit, Third-party advisory) - [exchange.xforce.ibmcloud.com](https://exchange.xforce.ibmcloud.com/vulnerabilities/96726) (Third-party advisory, Vulnerability database) ## Questions ### What is CVE-2014-7231? CVE-2014-7231 is a low-severity flaw in Cinder from Openstack, published on 8 October 2014. An attacker has to be already on the device without logging in. If it works, the attacker can read some data. ### How serious is CVE-2014-7231? It scores 2.1 out of 10 on the CVSS severity scale, which is low. Our risk score for CVE-2014-7231 is 30 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2014-7231 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 0.5%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2014-7231 affect? For Cinder from Openstack: 2013.2 to before 2013.2.4, 2014.1 to before 2014.1.3. The record lists 4 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2014-7231? Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2014-7231 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