# CVE-2012-0305: Privilege escalation in n/a

> Local attackers can escalate privileges by placing a malicious DLL in the current working directory of Symantec System Recovery.

- **Severity:** Medium 4.4 (`AV:L/AC:M/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:** 23 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2wh2-cqr6-7mp4

## What is CVE-2012-0305?

CVE-2012-0305 is a medium-severity vulnerability in n/a, published on 23 Jul 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in Symantec System Recovery 2011 before SP2 and Backup Exec System Recovery 2010 before SP5 allows local users to gain privileges via a Trojan horse DLL in the current working directory.

## Which versions are affected by CVE-2012-0305?

It affects 2 products.


Products: Symantec Backupexec System Recovery, Symantec System Recovery.

## How do I fix CVE-2012-0305?

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

## Is CVE-2012-0305 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-0457](https://insights.sbomify.com/CVE-2008-0457/): File upload in n/a (critical 10.0)
- [CVE-2007-4347](https://insights.sbomify.com/CVE-2007-4347/): Integer overflow in n/a (high 7.8)
- [CVE-2007-2359](https://insights.sbomify.com/CVE-2007-2359/): Memory corruption in n/a (high 7.2)
- [CVE-2007-2360](https://insights.sbomify.com/CVE-2007-2360/): Weak cryptography in n/a (medium 6.8)
- [CVE-2008-2512](https://insights.sbomify.com/CVE-2008-2512/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0305 and fix it if it is affected.

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

## Sources

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

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