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

> An attacker with a stale link can access all files of the user who created it after a system upgrade, leading to significant data exposure.

- **Severity:** High 7.5 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c9gx-8c9q-mpp9

## What is CVE-2021-41573?

CVE-2021-41573 is a high-severity vulnerability in n/a, published on 29 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hitachi Content Platform Anywhere (HCP-AW) 4.4.5 and later allows information disclosure. If authenticated user creates a link to a file or folder while the system was running version 4.3.x or earlier and then shares the link and then later deletes the file or folder without deleting the link and before the link expires. If the system has been upgraded to version 4.4.5 or 4.5.0 a malicious user with the link could browse and download all files of the authenticated user that created the link .

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

It affects 1 product.


Products: Hitachi Content Platform Anywhere.

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

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

## Is CVE-2021-41573 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41573 is a high-severity vulnerability in n/a, published on 29 Sep 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-41573 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-41573/ (Markdown: https://insights.sbomify.com/CVE-2021-41573/index.md)
```

## Sources

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

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