Gem replacement via mismatched specification names
Published Aug 17, 2023 · Updated Oct 1, 2024
Improper input validation in RubyGems.org before 2023-08-14 allows remote attackers to replace certain published gems. The upload path used Gem::Specification#original_name as the storage filename without ensuring that it matched the new version's full_name, so a crafted YAML gemspec addressed an existing object. The target must have a platform, version, or gem name matching /-\d/; replacement purges the CDN and serves the malicious gem to later downloaders.
Summary
What happened
Improper input validation in RubyGems.org before 2023-08-14 allows remote attackers to replace certain published gems. The upload path used Gem::Specification#original_name as the storage filename without ensuring that it matched the new version's full_name, so a crafted YAML gemspec addressed an existing object. The target must have a platform, version, or gem name matching /-\d/; replacement purges the CDN and serves the malicious gem to later downloaders.
The record
- CVE
- CVE-2023-40165
- Published
- Aug 17, 2023
- Updated
- Oct 1, 2024
- Vendor
- RubyGems
- Product
- RubyGems.org
- Classifications
- CWE-20, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 2023CVE publishedPublication date reported by the CVE source.
- Oct 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2023-08-14
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted YAML gemspec overwrite exampleproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo