Arbitrary command execution via pipe-prefixed tags filenames
Published Jul 29, 2021 · Updated Oct 15, 2024
OS command injection in RDoc 3.11 through 6.3.0 allows local users to execute arbitrary commands through a crafted project filename. The remove_unparseable method passes tags-suffixed filenames to Kernel#open, which treats a leading pipe as a command stream and invokes the trailing shell command. Exploitation requires a user to run rdoc on an attacker-controlled Ruby project, and commands execute with that user's privileges.
Summary
What happened
OS command injection in RDoc 3.11 through 6.3.0 allows local users to execute arbitrary commands through a crafted project filename. The remove_unparseable method passes tags-suffixed filenames to Kernel#open, which treats a leading pipe as a command stream and invokes the trailing shell command. Exploitation requires a user to run rdoc on an attacker-controlled Ruby project, and commands execute with that user's privileges.
The record
- CVE
- CVE-2021-31799
- Published
- Jul 29, 2021
- Updated
- Oct 15, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2021CVE publishedPublication date reported by the CVE source.
- Oct 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No public exploit references are available in this record.
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