# CVE-2015-4410: Moped Rubygem Data Injection Vulnerability

> Remote attackers can cause denial of service or cross-site scripting via crafted strings in the Moped BSON ObjectId validation method.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 20 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-4410, GHSA-f93j-hmcr-jcwh, SUSE-SU-2016:2019-1

## What is CVE-2015-4410?

CVE-2015-4410 is a high-severity cross-site scripting vulnerability in Fedoraproject Fedora, published on 20 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Moped::BSON::ObjecId.legal? method in rubygem-moped before commit dd5a7c14b5d2e466f7875d079af71ad19774609b allows remote attackers to cause a denial of service (worker resource consumption) or perform a cross-site scripting (XSS) attack via a crafted string.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-4410?

4 open source packages ship an affected version, including moped. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `moped` | RubyGems | All versions | 1.5.3 |
| `moped` | RubyGems | All versions | 1.5.3 |
| `moped` | RubyGems | From 2.0.0 | 2.0.5 |
| `moped` | RubyGems | From 2.0.0 | 2.0.5 |
| `rubygem-bson-1_11` | SUSE:OpenStack Cloud 5 | All versions | 1.11.1-9.1 |
| `rubygem-easy_diff` | SUSE:OpenStack Cloud 5 | All versions | 0.0.5-9.1 |
| `rubygem-redcarpet` | SUSE:OpenStack Cloud 5 | All versions | 3.2.3-9.1 |
| `rubygem-sprockets-2_11` | SUSE:OpenStack Cloud 5 | All versions | 2.11.3-11.1 |

Products: Fedoraproject Fedora, Moped Project Moped.

## How do I fix CVE-2015-4410?

Upgrade moped to a fixed version for your release line: 1.5.3 or 2.0.5.

## Is CVE-2015-4410 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4410 and fix it if it is affected.

What it is: CVE-2015-4410 is a high-severity cross-site scripting vulnerability in Fedoraproject Fedora, published on 20 Feb 2020. 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-2015-4410 in the wild and no public exploit code.

Affected packages and fixed versions:
- moped (RubyGems): affected all versions; fixed in 1.5.3
- moped (RubyGems): affected all versions; fixed in 1.5.3
- moped (RubyGems): affected from 2.0.0; fixed in 2.0.5
- moped (RubyGems): affected from 2.0.0; fixed in 2.0.5

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

## Sources

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

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