# CVE-2019-5804: Other in Chrome

> A local attacker can spoof domains via crafted names due to incorrect command line processing in Chrome.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** Yes
- **Published:** 23 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h52g-p85j-frqr, UBUNTU-CVE-2019-5804

## What is CVE-2019-5804?

CVE-2019-5804 is a medium-severity vulnerability in Google Chrome, published on 23 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect command line processing in Chrome in Google Chrome prior to 73.0.3683.75 allowed a local attacker to perform domain spoofing via a crafted domain name.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

It affects 3 products.


Products: Google Chrome, Opensuse Backports, Opensuse Leap.

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

Upgrade to a fixed version.

## Is CVE-2019-5804 being exploited?

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

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5804 is a medium-severity vulnerability in Google Chrome, published on 23 May 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-5804 in the wild and no public exploit code.

Affected product: Google Chrome. 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-5804/ (Markdown: https://insights.sbomify.com/CVE-2019-5804/index.md)
```

## Sources

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

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