# CVE-2022-3704: Ruby on Rails _table.html.erb cross site scripting

> Reported XSS in Rails routes table, though maintainers dispute validity; apply patch if concerned.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** BIT-rails-2022-3704, DEBIAN-CVE-2022-3704

## What is CVE-2022-3704?

CVE-2022-3704 is a low-severity cross-site scripting vulnerability in Rubyonrails Rails, published on 26 Oct 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability classified as problematic has been found in Ruby on Rails. This affects an unknown part of the file actionpack/lib/action_dispatch/middleware/templates/routes/_table.html.erb. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. The real existence of this vulnerability is still doubted at the moment. The name of the patch is be177e4566747b73ff63fd5f529fab564e475ed4. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-212319. NOTE: Maintainer declares that there isn’t a valid attack vector. The issue was wrongly reported as a security vulnerability by a non-member of the Rails team.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-707 (Improper Neutralization)

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

1 open source package ship an affected version, including rails. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rails` | Bitnami | All versions | None |

Products: Rubyonrails Rails.

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

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

## Is CVE-2022-3704 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3704 exists.

## Other vulnerabilities in Rubyonrails Rails

- [CVE-2013-0277](https://insights.sbomify.com/CVE-2013-0277/): Active Record contains deserialization of arbitrary YAML (critical 10.0)
- [CVE-2017-17916](https://insights.sbomify.com/CVE-2017-17916/): SQL injection in n/a (high 8.1)
- [CVE-2017-17917](https://insights.sbomify.com/CVE-2017-17917/): SQL injection in n/a (high 8.1)
- [CVE-2026-33195](https://insights.sbomify.com/CVE-2026-33195/): Rails Active Storage has possible Path Traversal in DiskService (high 8.0)
- [CVE-2024-26142](https://insights.sbomify.com/CVE-2024-26142/): Rails possible ReDoS vulnerability in Accept header parsing in Action Dispatch (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3704 is a low-severity cross-site scripting vulnerability in Rubyonrails Rails, published on 26 Oct 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3704 exists.

Affected packages and fixed versions:
- rails (Bitnami): affected all versions; no fix listed

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

## Sources

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

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