# CVE-2017-3212: Weak cryptography in Space Coast Credit Union Mobile

> Man-in-the-middle attackers can spoof servers and obtain sensitive information because the mobile app fails to verify SSL certificates.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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:** 5 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2017-5908, GHSA-6939-j3mf-8m46

## What is CVE-2017-3212?

CVE-2017-3212 is a medium-severity vulnerability in Space Coast Credit Union Mobile, published on 5 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Space Coast Credit Union Mobile app 2.2 for iOS and 2.1.0.1104 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-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2017-3212?

It affects 1 product.


Products: Sccu Space Coast Credit Union.

## How do I fix CVE-2017-3212?

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

## Is CVE-2017-3212 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3212 and fix it if it is affected.

What it is: CVE-2017-3212 is a medium-severity vulnerability in Space Coast Credit Union Mobile, published on 5 May 2017. 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-2017-3212 in the wild and no public exploit code.

Affected product: Space Coast Credit Union Mobile. 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-2017-3212/ (Markdown: https://insights.sbomify.com/CVE-2017-3212/index.md)
```

## Sources

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

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