# CVE-2022-38216: Mapbox is vulnerable to Integer Overflow

> An integer overflow in the Mapbox gl-native library allows out-of-bounds writes via large image dimensions, potentially crashing the application.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 16 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4696-g7jj-xg2h

## What is CVE-2022-38216?

CVE-2022-38216 is a high-severity vulnerability in Mapbox, published on 16 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An integer overflow exists in Mapbox's closed source gl-native library prior to version 10.6.1, which is bundled with multiple Mapbox products including open source libraries. The overflow is caused by large image height and width values when creating a new Image and allows for out of bounds writes, potentially crashing the Mapbox process.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2022-38216?

2 open source packages ship an affected version, including com.mapbox.mapboxsdk:mapbox-android-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.mapbox.mapboxsdk:mapbox-android-core` | Maven | All versions | 10.6.1 |
| `com.mapbox.mapboxsdk:mapbox-android-core` | Maven | All versions | 10.6.1 |

Products: Mapbox Maps Software Development Kit.

## How do I fix CVE-2022-38216?

Upgrade com.mapbox.mapboxsdk:mapbox-android-core to 10.6.1 or later.

## Is CVE-2022-38216 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38216 and fix it if it is affected.

What it is: CVE-2022-38216 is a high-severity vulnerability in Mapbox, published on 16 Aug 2022. 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-2022-38216 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.mapbox.mapboxsdk:mapbox-android-core (Maven): affected all versions; fixed in 10.6.1
- com.mapbox.mapboxsdk:mapbox-android-core (Maven): affected all versions; fixed in 10.6.1

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

## Sources

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

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