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

> Remote attackers can access the plaintext database password by requesting an unprotected configuration file in the Smartphone Pentest Framework.

- **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:** 20 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4vc4-vv83-m3fr

## What is CVE-2012-5696?

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

### Official description

Bulb Security Smartphone Pentest Framework (SPF) before 0.1.3 does not properly restrict access to frameworkgui/config, which allows remote attackers to obtain the plaintext database password via a direct request.

Weakness: CWE-264

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

It affects 1 product.


Products: Bulbsecurity Smartphone Pentest Framework.

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

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

## Is CVE-2012-5696 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5878](https://insights.sbomify.com/CVE-2012-5878/): Command injection in n/a (critical 9.8)
- [CVE-2012-5693](https://insights.sbomify.com/CVE-2012-5693/): Command injection in n/a (high 8.8)
- [CVE-2012-5694](https://insights.sbomify.com/CVE-2012-5694/): SQL injection in n/a (medium 6.8)
- [CVE-2012-5695](https://insights.sbomify.com/CVE-2012-5695/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-5697](https://insights.sbomify.com/CVE-2012-5697/): Misconfiguration in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5696 is a medium-severity vulnerability in n/a, published on 20 Oct 2014. 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-5696 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-5696/ (Markdown: https://insights.sbomify.com/CVE-2012-5696/index.md)
```

## Sources

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

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