# CVE-2016-7812: Weak cryptography in The Bank of Tokyo-Mitsubishi UFJ, Ltd. App for Android

> A man-in-the-middle attacker can downgrade TLS to SSLv3, allowing eavesdropping on encrypted communications in the banking app.

- **Severity:** Low 3.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **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:** 2 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w2r9-4jvf-qxv3

## What is CVE-2016-7812?

CVE-2016-7812 is a low-severity vulnerability in The Bank of Tokyo-Mitsubishi UFJ, Ltd. App for Android, published on 2 Aug 2017. 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 Bank of Tokyo-Mitsubishi UFJ, Ltd. App for Android ver5.3.1, ver5.2.2 and earlier allow a man-in-the-middle attacker to downgrade the communication between the app and the server from TLS v1.2 to SSL v3.0, which may result in the attacker to eavesdrop on an encrypted communication.

Weakness: CWE-310

## Which versions are affected by CVE-2016-7812?

It affects 1 product.


Products: Mufg Mitsubishi Ufj.

## How do I fix CVE-2016-7812?

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

## Is CVE-2016-7812 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7812 and fix it if it is affected.

What it is: CVE-2016-7812 is a low-severity vulnerability in The Bank of Tokyo-Mitsubishi UFJ, Ltd. App for Android, published on 2 Aug 2017. 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-2016-7812 in the wild and no public exploit code.

Affected product: The Bank of Tokyo-Mitsubishi UFJ, Ltd. App for Android. 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-2016-7812/ (Markdown: https://insights.sbomify.com/CVE-2016-7812/index.md)
```

## Sources

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

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