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

> Remote attackers can access the management service using a hardcoded password, leading to unauthorized control and data exposure.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/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:** 20 Aug 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8h29-3hc6-h9fv

## What is CVE-2012-4362?

CVE-2012-4362 is a medium-severity vulnerability in n/a, published on 20 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

hydra.exe in HP SAN/iQ before 9.5 on the HP Virtual SAN Appliance has a hardcoded password of L0CAlu53R for the global$agent account, which allows remote attackers to obtain access to a management service via a login: request to TCP port 13838.

Weakness: CWE-255

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

It affects 1 product.


Products: Hp San\/Iq.

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

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

## Is CVE-2012-4362 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4362 exists.

Public exploit code:

- HP VSA - Remote Command Execution (exploitdb)
- HP StorageWorks P4000 - Virtual SAN Appliance Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-2352](https://insights.sbomify.com/CVE-2013-2352/): Auth bypass in n/a (critical 9.4)
- [CVE-2012-2986](https://insights.sbomify.com/CVE-2012-2986/): Command injection in n/a (high 7.7)
- [CVE-2012-4361](https://insights.sbomify.com/CVE-2012-4361/): Command injection in n/a (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4362 is a medium-severity vulnerability in n/a, published on 20 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4362 exists.

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-4362/ (Markdown: https://insights.sbomify.com/CVE-2012-4362/index.md)
```

## Sources

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

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