What is CVE-2021-41003?A medium-severity flaw in Aruba 8320, explained.
CVE-2021-41003 is a medium-severity flaw (CVSS 6.1) in Aruba 8320 from HPE, published on 2 March 2022. 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.8%. If you run an affected version, plan in the vendor’s fix.
Published 2 March 2022. Record last updated 27 September 2022. We keep this page's data up to date.
What is CVE-2021-41003? In plain terms.
It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data.
Multiple unauthenticated command injection vulnerabilities were discovered in the AOS-CX API interface in Aruba CX 6200F Switch Series, Aruba 6300 Switch Series, Aruba 6400 Switch Series, Aruba 8320 Switch Series, Aruba 8325 Switch Series, Aruba 8400 Switch Series, Aruba CX 8360 Switch Series version(s): AOS-CX 10.06.xxxx: 10.06.0170 and below, AOS-CX 10.07.xxxx: 10.07.0050 and below, AOS-CX 10.08.xxxx: 10.08.1030 and below, AOS-CX 10.09.xxxx: 10.09.0002 and below. Aruba has released upgrades for Aruba AOS-CX devices that address these security vulnerabilities.
What kind of flaw is it?
- UnknownUnknown
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickYes, a person has to take an action
- What an attacker getsCan read some data and change some data
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Is CVE-2021-41003 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.8%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2021-41003 scores 25. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2021-41003 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2021-41003? 15 products.
The published record lists 15 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Hardware
Aruba 8320
by HPE
Affected versionsversion not specified - Operating system
Arubaos-Cx
by HPE
Affected versions10.06.0001 to 10.06.017010.07.0001 to 10.07.005010.08.0001 to 10.08.103010.09.0001 to 10.09.0002 - Hardware
Aruba 8325-32-C
by HPE
Affected versionsversion not specified - Hardware
Aruba 8325-48y8c
by HPE
Affected versionsversion not specified - Hardware
Aruba 8360-12c
by HPE
Affected versionsversion not specified - Hardware
Aruba 8360-16y2c
by HPE
Affected versionsversion not specified - Hardware
Aruba 8360-24xf2c
by HPE
Affected versionsversion not specified - Hardware
Aruba 8360-32y4c
by HPE
Affected versionsversion not specified - Hardware
Aruba 8360-48xt4c
by HPE
Affected versionsversion not specified
How do I fix CVE-2021-41003? Four steps.
- Check whether you run itCompare 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.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack 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.
Does CVE-2021-41003 affect you? 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
Multiple unauthenticated command injection vulnerabilities were discovered in the AOS-CX API interface in Aruba CX 6200F Switch Series, Aruba 6300 Switch Ser...
- Matched to
- Aruba 8320 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.
CVE-2021-41003 is a medium-severity flaw in Aruba 8320 from HPE, published on 2 March 2022. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data.
It scores 6.1 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2021-41003 is 25 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.
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.8%. That can change at any time, which is why we keep watching.
For Aruba 8320 from HPE: version not specified. The record lists 15 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.