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

> Authenticated remote attackers can access sensitive information in HP SQL/MX when SQL/MP Objects are enabled.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/A:N`)
- **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:** 28 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-frmx-52c6-484r

## What is CVE-2013-2322?

CVE-2013-2322 is a low-severity vulnerability in n/a, published on 28 Jun 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HP SQL/MX 3.2 and earlier on NonStop servers, when SQL/MP Objects are used, allows remote authenticated users to obtain sensitive information via unspecified vectors, aka the "SQL/MP index" issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Hp Nonstop Sql\/Mx.

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

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

## Is CVE-2013-2322 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2323](https://insights.sbomify.com/CVE-2013-2323/): Missing authorization in n/a (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2322 is a low-severity vulnerability in n/a, published on 28 Jun 2013. 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-2322 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-2322/ (Markdown: https://insights.sbomify.com/CVE-2013-2322/index.md)
```

## Sources

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

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