# CVE-2013-4575: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a heap-based buffer overflow in the Linux agent utility.

- **Severity:** High 7.9 (`AV:A/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mm43-pqgm-q482

## What is CVE-2013-4575?

CVE-2013-4575 is a high-severity memory corruption vulnerability in n/a, published on 4 Aug 2013. It can be exploited over the network, with no action from the victim.

### Official description

Heap-based buffer overflow in the utility program in the Linux agent in Symantec Backup Exec 2010 R3 before 2010 R3 SP3 and 2012 before SP2 allows remote attackers to cause a denial of service (agent crash) or possibly execute arbitrary code via unspecified vectors.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Symantec Backup Exec.

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

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

## Is CVE-2013-4575 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0546](https://insights.sbomify.com/CVE-2011-0546/): Auth bypass in n/a (medium 6.5)
- [CVE-2013-4676](https://insights.sbomify.com/CVE-2013-4676/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2013-4677](https://insights.sbomify.com/CVE-2013-4677/): Misconfiguration in n/a (medium 4.3)
- [CVE-2013-4678](https://insights.sbomify.com/CVE-2013-4678/): Information disclosure in n/a (low 2.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4575 is a high-severity memory corruption vulnerability in n/a, published on 4 Aug 2013. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4575 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-4575/ (Markdown: https://insights.sbomify.com/CVE-2013-4575/index.md)
```

## Sources

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

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