Storage Console vulnerabilitiesRanked by how likely they are to be used.
Storage Console is made by Red Hat. We track 3 published vulnerabilities listed under that exact name, across 1 version. None of them is on the list of flaws known to be exploited today. Red Hat lists newer releases under their own names, such as Storage Console Node, so check those pages too.
We keep watching the known-exploited list.
Is Storage Console listed under other names? Yes.
Red Hat also lists Storage Console under more specific names, such as Storage Console Node. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Storage Console vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Storage Console's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Storage Console flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 4.8%CVE-2017-7481Critical
Ansible before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe.
- 0.4%CVE-2016-7062High
rhscon-ceph in Red Hat Storage Console 2 x86_64 and Red Hat Storage Console Node 2 x86_64 allows local users to obtain the password as cleartext.
- 0.3%CVE-2017-2665High
The skyring-setup command creates random password for mongodb skyring database but it writes password in plain text to /etc/skyring/skyring.conf file which is owned by root but read by local user.
Running Storage Console? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Ansible before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated.
- Matched to
- Storage Console on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 3 published vulnerabilities listed under the name Storage Console, across 1 version.
None of Storage Console's vulnerabilities is on the list of flaws known to be exploited today.
Red Hat also lists Storage Console under more specific names, such as Storage Console Node. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Storage Console. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.