# CVE-2019-17624: Memory corruption in n/a

> A stack-based buffer overflow in X.Org X Server allows attackers to cause a denial of service via crafted input.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-76vq-rvvq-q48w

## What is CVE-2019-17624?

CVE-2019-17624 is a high-severity memory corruption vulnerability in X.org X Server, published on 16 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

"" In X.Org X Server 1.20.4, there is a stack-based buffer overflow in the function XQueryKeymap. For example, by sending ct.c_char 1000 times, an attacker can cause a denial of service (application crash) or possibly have unspecified other impact. Note: It is disputed if the X.Org X Server is involved or if there is a stack overflow.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-17624?

It affects 1 product.


Products: X.org X Server.

## How do I fix CVE-2019-17624?

No fix has been published for CVE-2019-17624 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-17624 being exploited?

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

Public exploit code:

- X.Org X Server 1.20.4 - Local Stack Overflow (exploitdb)

## Other vulnerabilities in X.org X Server

- [CVE-2026-56000](https://insights.sbomify.com/CVE-2026-56000/): xorg-x11-server / xwayland GLX contextTags Use-After-Free in CommonMakeCurrent() (critical 9.0)
- [CVE-2017-10971](https://insights.sbomify.com/CVE-2017-10971/): Memory corruption in n/a (high 8.8)
- [CVE-2026-55999](https://insights.sbomify.com/CVE-2026-55999/): xorg-server / xwayland glamor font atlas Heap Buffer Overflow (high 8.5)
- [CVE-2022-2319](https://insights.sbomify.com/CVE-2022-2319/): Memory corruption in xorg-x11-server (high 7.8)
- [CVE-2022-2320](https://insights.sbomify.com/CVE-2022-2320/): Memory corruption in xorg-x11-server (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17624 and fix it if it is affected.

What it is: CVE-2019-17624 is a high-severity memory corruption vulnerability in X.org X Server, published on 16 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17624 in the wild and no public exploit code.

Affected product: X.org X Server. 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-2019-17624/ (Markdown: https://insights.sbomify.com/CVE-2019-17624/index.md)
```

## Sources

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

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