# CVE-2022-28109: Server-side request forgery in n/a

> Remote attackers can execute arbitrary code on Selenium Grid servers via DNS rebinding attacks targeting the WebDriver endpoint.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r2fp-xp6r-99gj

## What is CVE-2022-28109?

CVE-2022-28109 is a high-severity server-side request forgery vulnerability in n/a, published on 15 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Selenium Selenium Grid (formerly Selenium Standalone Server) Fixed in 4.0.0-alpha-7 is affected by: DNS rebinding. The impact is: execute arbitrary code (remote). The component is: WebDriver endpoint of Selenium Grid / Selenium Standalone Server. The attack vector is: Triggered by browsing to to a malicious remote web server. The WebDriver endpoint of Selenium Server (Grid) is vulnerable to DNS rebinding. This can be used to execute arbitrary code on the machine.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Selenium Selenium Grid.

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

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

## Is CVE-2022-28109 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28108](https://insights.sbomify.com/CVE-2022-28108/): Selenium Server (Grid) CSRF (high 8.8)
- [CVE-2020-23452](https://insights.sbomify.com/CVE-2020-23452/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28109 is a high-severity server-side request forgery vulnerability in n/a, published on 15 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-28109 in the wild and no public exploit code.

Affected product: n/a. 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-2022-28109/ (Markdown: https://insights.sbomify.com/CVE-2022-28109/index.md)
```

## Sources

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

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