CVE-2021-25141: A security vulnerability has been identified in in certain HPE and Aruba L2/L3 switch firmware.
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A security vulnerability has been identified in in certain HPE and Aruba L2/L3 switch firmware. A data processing error due to improper handling of an unexpected data type in user supplied information to the switch's management interface has been identified. The data processing error could be exploited to cause a crash or reboot in the switch management interface and/or possibly the switch itself leading to local denial of service (DoS). The user must have administrator privileges to exploit this vulnerability.
- Published
- Feb 9, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- —
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hpe | 8200 zl firmware | cpe:2.3:o:hpe:8200_zl_firmware |
| hpe | 8200 zl | cpe:2.3:h:hpe:8200_zl |
| hpe | 6200 yl firmware | cpe:2.3:o:hpe:6200_yl_firmware |
| hpe | 6200 yl | cpe:2.3:h:hpe:6200_yl |
| hpe | 3500 firmware | cpe:2.3:o:hpe:3500_firmware |
| hpe | 3500 | cpe:2.3:h:hpe:3500 |
| hpe | 3500 yl firmware | cpe:2.3:o:hpe:3500_yl_firmware |
| hpe | 3500 yl | cpe:2.3:h:hpe:3500_yl |
| arubanetworks | aruba 5406r zl2 firmware | cpe:2.3:o:arubanetworks:aruba_5406r_zl2_firmware |
| arubanetworks | aruba 5406r zl2 | cpe:2.3:h:arubanetworks:aruba_5406r_zl2 |
| arubanetworks | aruba 5412r zl2 firmware | cpe:2.3:o:arubanetworks:aruba_5412r_zl2_firmware |
| arubanetworks | aruba 5412r zl2 | cpe:2.3:h:arubanetworks:aruba_5412r_zl2 |
and 18 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- arubanetworks aruba 2530ya firmwarebefore ya.16.10.0012
- arubanetworks aruba 2530yb firmwarebefore yb.16.10.0012
- arubanetworks aruba 2540 firmwarebefore yc.16.10.0012
- arubanetworks aruba 2620 firmwarebefore ra.16.04.0022
- arubanetworks aruba 2920 firmwarebefore wb.16.10.0011
- arubanetworks aruba 2930f firmwarebefore wc.16.10.0012
- arubanetworks aruba 2930m firmwarebefore wc.16.10.0012
- arubanetworks aruba 3800 firmwarebefore ka.16.04.0022
- arubanetworks aruba 3810m firmwarebefore kb.16.10.0012
- arubanetworks aruba 5406r zl2 firmwarebefore kb.16.10.0012
- arubanetworks aruba 5412r zl2 firmwarebefore kb.16.10.0012
- hpe 3500 firmwarebefore k.16.02.0032
- hpe 3500 yl firmwarebefore k.16.02.0032
- hpe 6200 yl firmwarebefore k.15.18.0024
- hpe 8200 zl firmwarebefore k.15.18.0024
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hpe). Independent of NVD's CPE analysis and usually ahead of it.
n/a Aruba 5400R zl2 Switch Series; Aruba 2930F Switch Series; Aruba 2920 Switch Series; Aruba 2930M Switch Series; Aruba 2530 Switch Series; Aruba 2540 Switch Series; Aruba 3800 Switch Series; HPE 3500 an
- Prior to KB.16.10.0012, - Prior to WC.16.10.0012, - Prior to WB.16.10.0011, - Aruba 2530YA prior to YA.16.10.0012 / Aruba 2530YB prior YB.16.10.0012, - Prior to YC.16.10.0012, - Prior to KA.16.04.0022, - Prior to K.16.02.0032, - Prior to KB.16.10.0012, - Prior to K.15.18.0024, - Prior to RA.16.04.0022affected
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.
No history yet (it accumulates with the daily EPSS job).
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
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
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.