# CVE-2018-16179: Security feature bypass in Mizuho Direct App for Android

> Attackers can intercept sensitive data via man-in-the-middle attacks because the app fails to verify server certificates.

- **Severity:** Medium 5.9 (`CVSS:3.0/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:** 9 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q3h8-vxrg-hgjp

## What is CVE-2018-16179?

CVE-2018-16179 is a medium-severity vulnerability in Mizuho Direct App for Android, published on 9 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Mizuho Direct App for Android version 3.13.0 and earlier does not verify server certificates, 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-2018-16179?

It affects 1 product.


Products: Mizuhobank Mizuho Direct Application.

## How do I fix CVE-2018-16179?

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

## Is CVE-2018-16179 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16179 and fix it if it is affected.

What it is: CVE-2018-16179 is a medium-severity vulnerability in Mizuho Direct App for Android, published on 9 Jan 2019. 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-2018-16179 in the wild and no public exploit code.

Affected product: Mizuho Direct 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-2018-16179/ (Markdown: https://insights.sbomify.com/CVE-2018-16179/index.md)
```

## Sources

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

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