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

> Remote attackers can sniff cleartext database credentials from the datasource editor when save-password is enabled, exposing sensitive information.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 29 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-975g-jv28-79r2

## What is CVE-2012-3312?

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

### Official description

The datasource definition editor in IBM InfoSphere Guardium 8.2 and earlier, when the save-password setting is enabled, transmits cleartext database credentials, which allows remote attackers to obtain sensitive information by sniffing the network.

Weakness: CWE-310

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

It affects 1 product.


Products: Ibm Infosphere Guardium.

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

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

## Is CVE-2012-3312 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0490](https://insights.sbomify.com/CVE-2013-0490/): Privilege escalation in n/a (high 7.2)
- [CVE-2012-3309](https://insights.sbomify.com/CVE-2012-3309/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-3341](https://insights.sbomify.com/CVE-2012-3341/): Cross-site scripting in InfoSphere Guardium (medium 6.4)
- [CVE-2012-3336](https://insights.sbomify.com/CVE-2012-3336/): SQL injection in InfoSphere Guardium (medium 6.3)
- [CVE-2012-2204](https://insights.sbomify.com/CVE-2012-2204/): InfoSphere Guardium aix_ktap module: DoS (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3312 is a medium-severity vulnerability in n/a, published on 29 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-3312 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-3312/ (Markdown: https://insights.sbomify.com/CVE-2012-3312/index.md)
```

## Sources

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

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