# CVE-2013-6212: Information disclosure in n/a

> Remote authenticated users can obtain sensitive information from HP Database and Middleware Automation via unspecified vectors.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-467f-8w98-m67h

## What is CVE-2013-6212?

CVE-2013-6212 is a medium-severity vulnerability in n/a, published on 19 Apr 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in HP Database and Middleware Automation 10.0, 10.01, 10.10, and 10.20 before 10.20.100 allows remote authenticated users to obtain sensitive information via unknown vectors.

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

It affects 1 product.


Products: Hp Database and Middleware Automation.

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

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

## Is CVE-2013-6212 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2365](https://insights.sbomify.com/CVE-2013-2365/): HP Database and Middleware Automation (DMA) 10.x before 10.10, when SSL is used, allows remote attackers to obtain sensitive information via unspecified vectors. (high 7.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6212 is a medium-severity vulnerability in n/a, published on 19 Apr 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6212 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-6212/ (Markdown: https://insights.sbomify.com/CVE-2013-6212/index.md)
```

## Sources

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

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