# CVE-2021-22267: Other in n/a

> Remote attackers can perform replay attacks against specific HPE NonStop Web ViewPoint Suite components, bypassing authentication or session controls.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fv88-77rc-98g3

## What is CVE-2021-22267?

CVE-2021-22267 is a medium-severity vulnerability in n/a, published on 9 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Idelji Web ViewPoint Suite, as used in conjunction with HPE NonStop, allows a remote replay attack for T0320L01^ABP through T0320L01^ABZ, T0952L01^AAH through T0952L01^AAR, T0986L01 through T0986L01^AAF, T0665L01^AAP, and T0662L01^AAP (L) and T0320H01^ABO through T0320H01^ABY, T0952H01^AAG through T0952H01^AAQ, T0986H01 through T0986H01^AAE, T0665H01^AAO, and T0662H01^AAO (J and H).

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Hpe Web Viewpoint.

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

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

## Is CVE-2021-22267 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-3191](https://insights.sbomify.com/CVE-2021-3191/): Auth bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22267 is a medium-severity vulnerability in n/a, published on 9 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22267 in the wild and no public exploit code.

Affected product: n/a. 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-22267/ (Markdown: https://insights.sbomify.com/CVE-2021-22267/index.md)
```

## Sources

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

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