# CVE-2012-0126: Information disclosure in n/a

> Remote attackers can access diagnostic information in HP-UX WBEM implementation, exposing sensitive system data.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c9x4-2q4c-f8c7

## What is CVE-2012-0126?

CVE-2012-0126 is a medium-severity vulnerability in Hp Hp-Ux, published on 28 Mar 2012. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the WBEM implementation in HP HP-UX 11.11 and 11.23 allows remote attackers to obtain access to diagnostic information via unknown vectors, a related issue to CVE-2012-0125.

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

It affects 1 product.


Products: Hp Hp-Ux.

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

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

## Is CVE-2012-0126 being exploited?

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

## Other vulnerabilities in Hp Hp-Ux

- [CVE-2008-1668](https://insights.sbomify.com/CVE-2008-1668/): Privilege escalation in n/a (critical 10.0)
- [CVE-2008-1662](https://insights.sbomify.com/CVE-2008-1662/): Missing authorization in n/a (critical 10.0)
- [CVE-2007-6425](https://insights.sbomify.com/CVE-2007-6425/): Denial of service in n/a (critical 10.0)
- [CVE-2007-6195](https://insights.sbomify.com/CVE-2007-6195/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-4241](https://insights.sbomify.com/CVE-2007-4241/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-0126 is a medium-severity vulnerability in Hp Hp-Ux, published on 28 Mar 2012. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0126 in the wild and no public exploit code.

Affected product: Hp Hp-Ux. 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-0126/ (Markdown: https://insights.sbomify.com/CVE-2012-0126/index.md)
```

## Sources

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

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