# CVE-2021-3191: Auth bypass in n/a

> Remote attackers can bypass authentication to gain unauthorized access to specific HPE NonStop Web ViewPoint Suite components.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-m459-j5mw-gjwx

## What is CVE-2021-3191?

CVE-2021-3191 is a high-severity authentication bypass vulnerability in n/a, published on 9 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Idelji Web ViewPoint Suite, as used in conjunction with HPE NonStop, allows Remote Unauthorized Access for T0320L01^ABY and T0320L01^ACD, T0952L01^AAR through T0952L01^AAX, and T0986L01^AAD through T0986L01^AAJ (L) and T0320H01^ABW through T0320H01^ACC, T0952H01^AAQ through T0952H01^AAW, and T0986H01^AAC through T0986H01^AAI (J and H).

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

It affects 1 product.


Products: Hpe Web Viewpoint.

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

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

## Is CVE-2021-3191 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-22267](https://insights.sbomify.com/CVE-2021-22267/): Other in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3191 is a high-severity authentication bypass vulnerability in n/a, published on 9 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3191 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-3191/ (Markdown: https://insights.sbomify.com/CVE-2021-3191/index.md)
```

## Sources

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

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