# CVE-2020-3996: Information disclosure in Velero

> Velero fails to properly manage volume identifiers, potentially allowing unauthorized users to access sensitive information.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-72xg-3mcq-52v4, openSUSE-SU-2024:11494-1

## What is CVE-2020-3996?

CVE-2020-3996 is a medium-severity vulnerability in Velero, published on 22 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Velero (prior to 1.4.3 and 1.5.2) in some instances doesn’t properly manage volume identifiers which may result in information leakage to unauthorized users.

## Which versions are affected by CVE-2020-3996?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `velero` | openSUSE:Tumbleweed | All versions | 1.6.3-1.2 |

Products: Vmware Velero.

## How do I fix CVE-2020-3996?

Upgrade to a fixed version.

## Is CVE-2020-3996 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3996 and fix it if it is affected.

What it is: CVE-2020-3996 is a medium-severity vulnerability in Velero, published on 22 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-3996 in the wild and no public exploit code.

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

## Sources

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

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