# CVE-2024-35221: Denial of service when publishing a package on rubygems.org > A remote attacker can cause a denial of service on rubygems.org by publishing a gem with malicious YAML aliases, requiring a patch to the platform. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 May 2024 - **Updated:** 2 Aug 2024 - **Also known as:** OESA-2024-1780, OESA-2024-1938, SUSE-SU-2025:02814-1, SUSE-SU-2025:02814-2 ## What is CVE-2024-35221? CVE-2024-35221 is a medium-severity denial of service vulnerability in rubygems.org, published on 29 May 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Rubygems.org is the Ruby community's gem hosting service. A Gem publisher can cause a Remote DoS when publishing a Gem. This is due to how Ruby reads the Manifest of Gem files when using Gem::Specification.from_yaml. from_yaml makes use of SafeYAML.load which allows YAML aliases inside the YAML-based metadata of a gem. YAML aliases allow for Denial of Service attacks with so-called `YAML-bombs` (comparable to Billion laughs attacks). This was patched. There is is no action required by users. This issue is also tracked as GHSL-2024-001 and was discovered by the GitHub security lab. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2024-35221? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ruby2.5` | SUSE:Enterprise Storage 7.1 | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Manager Proxy LTS 4.3 | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | SUSE:Manager Server LTS 4.3 | All versions | 2.5.9-150000.4.49.1 | | `ruby2.5` | openSUSE:Leap 15.6 | All versions | 2.5.9-150000.4.49.1 | ## How do I fix CVE-2024-35221? Apply the vendor's patch. ## Is CVE-2024-35221 being exploited? There is no known exploitation of CVE-2024-35221 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-35221 and fix it if it is affected. What it is: CVE-2024-35221 is a medium-severity denial of service vulnerability in rubygems.org, published on 29 May 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-35221 in the wild and no public exploit code. Affected product: rubygems.org. 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-2024-35221/ (Markdown: https://insights.sbomify.com/CVE-2024-35221/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-35221 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-35221 - OSV: https://osv.dev/vulnerability/CVE-2024-35221 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-35221/ Summaries are generated and may contain mistakes; the official description above is the record.