# CVE-2021-22887: Other in PSA5000, PSA7000

> An attacker who has already compromised the device can exploit a BIOS vulnerability to compromise firmware on Pulse Secure PSA-Series hardware.

- **Severity:** Low 2.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gpmr-cr86-wc6h

## What is CVE-2021-22887?

CVE-2021-22887 is a low-severity vulnerability in PSA5000, PSA7000, published on 16 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the BIOS of Pulse Secure (PSA-Series Hardware) models PSA5000 and PSA7000 could allow an attacker to compromise BIOS firmware. This vulnerability can be exploited only as part of an attack chain. Before an attacker can compromise the BIOS, they must exploit the device.

Weakness: CWE-506 (Embedded Malicious Code)

## Which versions are affected by CVE-2021-22887?

It affects 12 products.


Products: Pulsesecure Psa-5000 Firmware, Pulsesecure Psa-7000 Firmware, Supermicro X10sl7-F Firmware, Supermicro X10sla-F Firmware, Supermicro X10slh-F Firmware, Supermicro X10sll-F Firmware, Supermicro X10sll-S Firmware, Supermicro X10sll-Sf Firmware, Supermicro X10sll\+f Firmware, Supermicro X10slm-F Firmware, Supermicro X10slm\+-F Firmware, Supermicro X10slm\+ln4f Firmware.

## How do I fix CVE-2021-22887?

No fix has been published for CVE-2021-22887 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-22887 being exploited?

There is no known exploitation of CVE-2021-22887 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22887 and fix it if it is affected.

What it is: CVE-2021-22887 is a low-severity vulnerability in PSA5000, PSA7000, published on 16 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22887 in the wild and no public exploit code.

Affected product: PSA5000, PSA7000. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-22887/ (Markdown: https://insights.sbomify.com/CVE-2021-22887/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-22887
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-22887
- OSV: https://osv.dev/vulnerability/CVE-2021-22887

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-22887/
Summaries are generated and may contain mistakes; the official description above is the record.