# CVE-2012-3270: Other in n/a

> Remote attackers can obtain sensitive information, modify data, or cause denial of service in HP Performance Insight when using Sybase.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 7 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w368-gg7c-hh3v

## What is CVE-2012-3270?

CVE-2012-3270 is a critical vulnerability in n/a, published on 7 Nov 2012. It can be exploited over the network.

### Official description

Unspecified vulnerability in HP Performance Insight 5.31, 5.40, and 5.41, when Sybase is used, allows remote attackers to obtain sensitive information, modify data, or cause a denial of service via unknown vectors, a different vulnerability than CVE-2012-3269.

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

It affects 1 product.


Products: Hp Performance Insight.

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

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

## Is CVE-2012-3270 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3096](https://insights.sbomify.com/CVE-2009-3096/): Other in n/a (critical 10.0)
- [CVE-2012-2009](https://insights.sbomify.com/CVE-2012-2009/): Privilege escalation in n/a (critical 9.0)
- [CVE-2009-3097](https://insights.sbomify.com/CVE-2009-3097/): Information disclosure in n/a (high 7.8)
- [CVE-2012-3269](https://insights.sbomify.com/CVE-2012-3269/): Other in n/a (high 7.5)
- [CVE-2012-2007](https://insights.sbomify.com/CVE-2012-2007/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3270 is a critical vulnerability in n/a, published on 7 Nov 2012. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2012-3270 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-3270/ (Markdown: https://insights.sbomify.com/CVE-2012-3270/index.md)
```

## Sources

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

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