# CVE-2023-3782: Denial of service in squareup:okhttp-brotli

> An attacker can cause a denial of service in OkHttp clients using BrotliInterceptor by serving malicious compressed data or via Man-in-the-Middle attacks.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2023
- **Updated:** 28 Oct 2024
- **Also known as:** CLSA-2026-1787931895, GHSA-w28c-cgxf-w8gv

## What is CVE-2023-3782?

CVE-2023-3782 is a medium-severity denial of service vulnerability in squareup:okhttp-brotli, published on 19 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DoS of the OkHttp client when using a BrotliInterceptor and surfing to a malicious web server, or when an attacker can perform MitM to inject a Brotli zip-bomb into an HTTP response

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2023-3782?

It affects 1 product.


Products: Squareup Okhttp-Brotli.

## How do I fix CVE-2023-3782?

Upgrade to a fixed version.

## Is CVE-2023-3782 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3782 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3782 and fix it if it is affected.

What it is: CVE-2023-3782 is a medium-severity denial of service vulnerability in squareup:okhttp-brotli, published on 19 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3782 exists.

Affected product: squareup:okhttp-brotli. 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-2023-3782/ (Markdown: https://insights.sbomify.com/CVE-2023-3782/index.md)
```

## Sources

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

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