# CVE-2012-4610: Hardcoded credentials in n/a

> Remote attackers can obtain the cleartext root password stored on the proxy client, leading to sensitive information disclosure and potential privilege escalation.

- **Severity:** Low 3.3 (`AV:A/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3r4r-6824-gpc7

## What is CVE-2012-4610?

CVE-2012-4610 is a low-severity vulnerability in n/a, published on 31 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EMC Avamar Client for VMware 6.1 stores the cleartext server root password on the proxy client, which might allow remote attackers to obtain sensitive information by leveraging "network access" to the proxy client.

Weakness: CWE-255

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

It affects 1 product.


Products: Emc Avamar.

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

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

## Is CVE-2012-4610 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0945](https://insights.sbomify.com/CVE-2013-0945/): Security feature bypass in n/a (critical 9.3)
- [CVE-2016-0906](https://insights.sbomify.com/CVE-2016-0906/): Missing authorization in n/a (high 8.8)
- [CVE-2011-0648](https://insights.sbomify.com/CVE-2011-0648/): Privilege escalation in n/a (high 8.5)
- [CVE-2011-1740](https://insights.sbomify.com/CVE-2011-1740/): Missing authorization in n/a (high 7.7)
- [CVE-2012-2291](https://insights.sbomify.com/CVE-2012-2291/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4610 is a low-severity vulnerability in n/a, published on 31 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-4610 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-4610/ (Markdown: https://insights.sbomify.com/CVE-2012-4610/index.md)
```

## Sources

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

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