# CVE-2012-5693: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in multiple parameters of the Smartphone Pentest Framework.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-98g9-jfv6-r2r5

## What is CVE-2012-5693?

CVE-2012-5693 is a high-severity command injection vulnerability in n/a, published on 3 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Bulb Security Smartphone Pentest Framework (SPF) before 0.1.3 allows remote attackers to execute arbitrary commands via shell metacharacters in the ipAddressTB parameter to (1) remoteAttack.pl or (2) guessPassword.pl in frameworkgui/; the filename parameter to (3) CSAttack.pl or (4) SEAttack.pl in frameworkgui/; the phNo2Attack parameter to (5) CSAttack.pl or (6) SEAttack.pl in frameworkgui/; the (7) platformDD2 parameter to frameworkgui/SEAttack.pl; the (8) agentURLPath or (9) agentControlKey parameter to frameworkgui/attach2agents.pl; or the (10) controlKey parameter to frameworkgui/attachMobileModem.pl. NOTE: The hostingPath parameter to CSAttack.pl and SEAttack.pl vectors and the appURLPath parameter to attachMobileModem.pl vector are covered by CVE-2012-5878.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Bulbsecurity Smartphone Pentest Framework.

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

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

## Is CVE-2012-5693 being exploited?

There is no known exploitation of CVE-2012-5693 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-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-5696](https://insights.sbomify.com/CVE-2012-5696/): Information disclosure in n/a (medium 5.0)
- [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-5693 and fix it if it is affected.

What it is: CVE-2012-5693 is a high-severity command injection vulnerability in n/a, published on 3 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-5693 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-5693/ (Markdown: https://insights.sbomify.com/CVE-2012-5693/index.md)
```

## Sources

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

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