# CVE-2021-3528: Information disclosure in NooBaa

> Attackers with log access can steal leaked AuthTokens to read and modify NooBaa system configuration.

- **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:** 13 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3q58-8ch7-h333

## What is CVE-2021-3528?

CVE-2021-3528 is a high-severity vulnerability in NooBaa, published on 13 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in noobaa-operator in versions before 5.7.0, where internal RPC AuthTokens between the noobaa operator and the noobaa core are leaked into log files. An attacker with access to the log files could use this AuthToken to gain additional access into noobaa deployment and can read/modify system configuration.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Redhat Noobaa-Operator.

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

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

## Is CVE-2021-3528 being exploited?

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

## Other vulnerabilities in NooBaa

- [CVE-2021-3529](https://insights.sbomify.com/CVE-2021-3529/): Cross-site scripting in noobaa-core (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3528 is a high-severity vulnerability in NooBaa, published on 13 May 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-3528 in the wild and no public exploit code.

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

## Sources

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

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