SAN Volume Controller Firmware vulnerabilitiesAnd the versions its exploited flaws hit.
SAN Volume Controller Firmware is made by IBM. We track 14 published vulnerabilities in it, across 63 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 28 January 2022. If you run SAN Volume Controller Firmware, check your version against the exploited flaws below and patch those first.
The most recent SAN Volume Controller Firmware flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022. We keep watching the known-exploited list.
Which versions of SAN Volume Controller Firmware do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "1.1.0.0 to before 7.1.0.11" means from 1.1.0.0 up to, but not including, 7.1.0.11. Find your version, then patch.
- CVE-2014-6271Exploited list, 28 Jan 2022
GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
1.1.0.0 to before 7.1.0.117.2.0.0 to before 7.2.0.97.3.0.0 to before 7.3.0.7 - CVE-2014-7169Exploited list, 28 Jan 2022
GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
1.1.0.0 to before 7.1.0.117.2.0.0 to before 7.2.0.97.3.0.0 to before 7.3.0.7
Which SAN Volume Controller Firmware vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.
- 9.8GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.
Which SAN Volume Controller Firmware 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.
- >99%
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment, as demonstrated by...
- >99%
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or possibly have unknown...
- 3.5%CVE-2017-1710Critical
A vulnerability in the Service Assistant GUI in IBM Storwize V7000 (2076) 8.1 could allow a remote attacker to perform a privilege escalation.
- 2.5%CVE-2018-1433High
IBM SAN Volume Controller, IBM Storwize, IBM Spectrum Virtualize and IBM FlashSystem products ( 6.1, 6.2, 6.3, 6.4, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.6.1, 7.7, 7.7.1, 7.8, 7.8.1, 8.1, and 8.1.1) web handler...
- 2.2%CVE-2018-1438High
IBM SAN Volume Controller, IBM Storwize, IBM Spectrum Virtualize and IBM FlashSystem products ( 6.1, 6.2, 6.3, 6.4, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.6.1, 7.7, 7.7.1, 7.8, 7.8.1, 8.1, and 8.1.1) web handler /DLSnap...
- 1.6%CVE-2018-1464Medium
IBM SAN Volume Controller, IBM Storwize, IBM Spectrum Virtualize and IBM FlashSystem products ( 6.1, 6.2, 6.3, 6.4, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.6.1, 7.7, 7.7.1, 7.8, 7.8.1, 8.1, and 8.1.1) could allow an...
- 1.6%CVE-2020-4686High
IBM Spectrum Virtualize 8.3.1 could allow a remote user authenticated via LDAP to escalate their privileges and perform actions they should not have access to.
- 1.5%CVE-2021-29873High
IBM Flash System 900 could allow an authenticated attacker to obtain sensitive information and cause a denial of service due to a restricted shell escape vulnerability.
- 1.4%CVE-2018-1463Medium
IBM SAN Volume Controller, IBM Storwize, IBM Spectrum Virtualize and IBM FlashSystem products ( 6.1, 6.2, 6.3, 6.4, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.6.1, 7.7, 7.7.1, 7.8, 7.8.1, 8.1, and 8.1.1) could allow an...
- 1.3%CVE-2018-1465Medium
IBM SAN Volume Controller, IBM Storwize, IBM Spectrum Virtualize and IBM FlashSystem products ( 6.1, 6.2, 6.3, 6.4, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.6.1, 7.7, 7.7.1, 7.8, 7.8.1, 8.1, and 8.1.1) could allow an...
Running SAN Volume Controller Firmware? 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 flaw being exploited affects software Acme tracks
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.
- Matched to
- SAN Volume Controller Firmware on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 14 published vulnerabilities listed under the name SAN Volume Controller Firmware, across 63 versions. The most recent SAN Volume Controller Firmware flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2014-6271 and CVE-2014-7169.
Each flaw names its own versions, usually as ranges. The newest, CVE-2014-6271, affects 1.1.0.0 to before 7.1.0.11, 7.2.0.0 to before 7.2.0.9, 7.3.0.0 to before 7.3.0.7. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track SAN Volume Controller Firmware. 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.