# CVE-2013-5008: Hardcoded credentials in n/a

> Local attackers can exploit a shared encryption key to access sensitive package-server information or cause denial of service in Symantec Management Platform.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 10 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vmv6-chfj-88gf

## What is CVE-2013-5008?

CVE-2013-5008 is a medium-severity vulnerability in n/a, published on 10 Oct 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The agent and task-agent components in Symantec Management Platform 7.0 and 7.1 before 7.1 SP2 Mp1.1v7 rollup, as used in certain Altiris products, use the same registry-entry encryption key across different customers' installations, which makes it easier for local users to obtain sensitive information about package-server access, or cause a denial of service, by leveraging knowledge of this key.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-5008?

It affects 1 product.


Products: Symantec Management Platform.

## How do I fix CVE-2013-5008?

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

## Is CVE-2013-5008 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5008 and fix it if it is affected.

What it is: CVE-2013-5008 is a medium-severity vulnerability in n/a, published on 10 Oct 2013. 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-2013-5008 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-2013-5008/ (Markdown: https://insights.sbomify.com/CVE-2013-5008/index.md)
```

## Sources

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

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