# CVE-2020-5832: Privilege escalation in Data Center Security Manager Component

> An attacker can exploit a privilege escalation vulnerability in Symantec Data Center Security Manager to gain elevated access to protected resources.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r9p7-fvg8-jvc8

## What is CVE-2020-5832?

CVE-2020-5832 is a high-severity vulnerability in Data Center Security Manager Component, published on 6 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Symantec Data Center Security Manager Component, prior to 6.8.2 (aka 6.8 MP2), may be susceptible to a privilege escalation vulnerability, which is a type of issue whereby an attacker may attempt to compromise the software application to gain elevated access to resources that are normally protected from an application or user.

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

It affects 1 product.


Products: Symantec Data Center Security.

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

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

## Is CVE-2020-5832 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-5832 is a high-severity vulnerability in Data Center Security Manager Component, published on 6 Apr 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-5832 in the wild and no public exploit code.

Affected product: Data Center Security Manager Component. 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-5832/ (Markdown: https://insights.sbomify.com/CVE-2020-5832/index.md)
```

## Sources

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

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