# CVE-2017-1000121: Integer overflow in n/a

> A compromised secondary process can trigger an integer overflow leading to a buffer overflow in the UI process, potentially allowing code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 1 Nov 2017
- **Updated:** 14 Nov 2024
- **Also known as:** DEBIAN-CVE-2017-1000121, GHSA-rv46-gc6r-8ffx, UBUNTU-CVE-2017-1000121

## What is CVE-2017-1000121?

CVE-2017-1000121 is a critical vulnerability in Webkitgtk Webkitgtk\+, published on 1 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The UNIX IPC layer in WebKit, including WebKitGTK+ prior to 2.16.3, does not properly validate message size metadata, allowing a compromised secondary process to trigger an integer overflow and subsequent buffer overflow in the UI process. This vulnerability does not affect Apple products.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2017-1000121?

It affects 1 product.


Products: Webkitgtk Webkitgtk\+.

## How do I fix CVE-2017-1000121?

Upgrade to a fixed version.

## Is CVE-2017-1000121 being exploited?

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

## Other vulnerabilities in Webkitgtk Webkitgtk\+

- [CVE-2018-11712](https://insights.sbomify.com/CVE-2018-11712/): Security feature bypass in n/a (high 7.5)
- [CVE-2018-11646](https://insights.sbomify.com/CVE-2018-11646/): Null dereference in n/a (high 7.5)
- [CVE-2017-1000122](https://insights.sbomify.com/CVE-2017-1000122/): Denial of service in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000121 and fix it if it is affected.

What it is: CVE-2017-1000121 is a critical vulnerability in Webkitgtk Webkitgtk\+, published on 1 Nov 2017. 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-2017-1000121 in the wild and no public exploit code.

Affected product: Webkitgtk Webkitgtk\+. 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-2017-1000121/ (Markdown: https://insights.sbomify.com/CVE-2017-1000121/index.md)
```

## Sources

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

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