# CVE-2021-43271: Information disclosure in n/a

> Riverbed AppResponse logs incorrect login credentials in WebUI logs, potentially exposing sensitive data to users with diagnostic access.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jun 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wm99-v254-v5x2

## What is CVE-2021-43271?

CVE-2021-43271 is a medium-severity vulnerability in n/a, published on 3 Jun 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Riverbed AppResponse 11.8.0, 11.8.5, 11.8.5a, 11.9.0, 11.9.0a, 11.10.0, 11.11.0, 11.11.0a, 11.11.1, 11.11.1a, 11.11.5, and 11.11.5a (when configured to use local, RADIUS, or TACACS authentication) logs usernames and passwords if either is entered incorrectly. If a user enters an incorrect username and/or password when logging into the WebUI, these attempted credentials are included in an error message that is logged in the WebUI log file. A log entry does not appear if the username and password provided correctly match a valid set of credentials. This also does not happen if AppResponse is configured to use SAML authentication. The WebUI log file is included in subsequent diagnostic system dumps that are generated. (Only users with Full Control access to the System Configuration permission can generate system dumps. By default, only System Administrators have Full Control access to the System Configuration permission.)

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Riverbed Appresponse.

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

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

## Is CVE-2021-43271 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-43271 is a medium-severity vulnerability in n/a, published on 3 Jun 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-43271 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-43271/ (Markdown: https://insights.sbomify.com/CVE-2021-43271/index.md)
```

## Sources

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

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