# CVE-2014-7804: Weak cryptography in n/a

> Man-in-the-middle attackers can spoof servers and obtain sensitive information due to missing X.509 certificate verification in the Android application.

- **Severity:** Medium 5.4 (`AV:A/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-48j8-pv27-h2vc

## What is CVE-2014-7804?

CVE-2014-7804 is a medium-severity vulnerability in n/a, published on 21 Oct 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Gangsta Auto Thief III (aka com.apptreestudios.gdup3) application 1.1 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

Weakness: CWE-310

## Which versions are affected by CVE-2014-7804?

It affects 1 product.


Products: Apptreestudios Gangsta Auto Thief Iii.

## How do I fix CVE-2014-7804?

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

## Is CVE-2014-7804 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7804 and fix it if it is affected.

What it is: CVE-2014-7804 is a medium-severity vulnerability in n/a, published on 21 Oct 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-7804 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-2014-7804/ (Markdown: https://insights.sbomify.com/CVE-2014-7804/index.md)
```

## Sources

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

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