IBM Spectrum Virtualize 8.3.1 could allow a remote user authenticated via LDAP to escalate their privileges and perform actions they should
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. IBM X-Force ID: 186678.
- Published
- Aug 17, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 75th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
CNA vs NVD score
- NVD
- 8.1
- CNA · ibm
- 6.8
- 1.3 point gap
CVSS:3.0/C:H/AV:N/PR:L/UI:N/I:H/S:U/AC:H/A:N/RL:O/E:U/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| ibm | spectrum virtualize | cpe:2.3:a:ibm:spectrum_virtualize |
| ibm | flashsystem v5000 firmware | cpe:2.3:o:ibm:flashsystem_v5000_firmware |
| ibm | flashsystem v5000 | cpe:2.3:h:ibm:flashsystem_v5000 |
| ibm | flashsystem v7200 firmware | cpe:2.3:o:ibm:flashsystem_v7200_firmware |
| ibm | flashsystem v7200 | cpe:2.3:h:ibm:flashsystem_v7200 |
| ibm | flashsystem v9000 firmware | cpe:2.3:o:ibm:flashsystem_v9000_firmware |
| ibm | flashsystem v9000 | cpe:2.3:h:ibm:flashsystem_v9000 |
| ibm | flashsystem v9100 firmware | cpe:2.3:o:ibm:flashsystem_v9100_firmware |
| ibm | flashsystem v9100 | cpe:2.3:h:ibm:flashsystem_v9100 |
| ibm | flashsystem v9200 firmware | cpe:2.3:o:ibm:flashsystem_v9200_firmware |
| ibm | flashsystem v9200 | cpe:2.3:h:ibm:flashsystem_v9200 |
| ibm | san volume controller firmware | cpe:2.3:o:ibm:san_volume_controller_firmware |
and 9 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm flashsystem v5000 firmware8.3.1
- ibm flashsystem v7200 firmware8.3.1
- ibm flashsystem v9000 firmware8.3.1
- ibm flashsystem v9100 firmware8.3.1
- ibm flashsystem v9200 firmware8.3.1
- ibm san volume controller firmware8.3.1
- ibm spectrum virtualize8.3.1
- ibm storwize v5000 firmware8.3.1
- ibm storwize v5000e firmware8.3.1
- ibm storwize v5100 firmware8.3.1
- ibm storwize v7000 firmware8.3.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM SAN Volume Controller and Storwize Family
- 8.3.1affected
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-38969IBM Spectrum Virtualize 8.2, 8.3, and 8.4 could allow an attacker to allow unauthorized access due to the reuse of support generated credent39Monitor
- CVE-2022-43873IBM Spectrum Virtualize privilege escalation35Monitor
- CVE-2021-29873IBM Flash System 900 could allow an authenticated attacker to obtain sensitive information and cause a denial of service due to a restricted32Monitor
- CVE-2023-25681IBM Spectrum Virtualize security bypass26Monitor
- CVE-2022-43870IBM Spectrum Virtualize information disclosure26Monitor
- CVE-2023-27870IBM Spectrum Virtualize information disclosure23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.