# CVE-2013-7398: Insufficient Verification of Data Authenticity in Async Http Client

> Man-in-the-middle attackers can spoof HTTPS servers because the library fails to verify hostnames in X.509 certificates.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5c66-6h6g-6q6m

## What is CVE-2013-7398?

CVE-2013-7398 is a medium-severity vulnerability in n/a, published on 24 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

main/java/com/ning/http/client/AsyncHttpClientConfig.java in Async Http Client (aka AHC or async-http-client) before 1.9.0 does not require a hostname match during verification of X.509 certificates, which allows man-in-the-middle attackers to spoof HTTPS servers via an arbitrary valid certificate.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2013-7398?

2 open source packages ship an affected version, including com.ning:async-http-client. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.ning:async-http-client` | Maven | All versions | 1.9.0 |
| `com.ning:async-http-client` | Maven | All versions | 1.9.0 |

Products: Async-Http-Client Project Async-Http-Client, Redhat Jboss Fuse.

## How do I fix CVE-2013-7398?

Upgrade com.ning:async-http-client to 1.9.0 or later.

## Is CVE-2013-7398 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-7397](https://insights.sbomify.com/CVE-2013-7397/): Insufficient Verification of Data Authenticity in Async Http Client (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7398 and fix it if it is affected.

What it is: CVE-2013-7398 is a medium-severity vulnerability in n/a, published on 24 Jun 2015. 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-2013-7398 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.ning:async-http-client (Maven): affected all versions; fixed in 1.9.0
- com.ning:async-http-client (Maven): affected all versions; fixed in 1.9.0

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-2013-7398/ (Markdown: https://insights.sbomify.com/CVE-2013-7398/index.md)
```

## Sources

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

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