Shell command execution via pipe-prefixed path
Published Jan 22, 2020 · Updated Aug 4, 2024
OS command injection in BibTeX-Ruby before 5.1.0 allows attackers to execute shell commands through a crafted bibliography path. BibTeX.open passes the path directly to Kernel.open, which interprets a leading pipe as a command instead of treating the value only as a file path. Exploitation requires an application to pass an attacker-controlled path to BibTeX.open, and commands run with the privileges of the hosting Ruby process.
Summary
What happened
OS command injection in BibTeX-Ruby before 5.1.0 allows attackers to execute shell commands through a crafted bibliography path. BibTeX.open passes the path directly to Kernel.open, which interprets a leading pipe as a command instead of treating the value only as a file path. Exploitation requires an application to pass an attacker-controlled path to BibTeX.open, and commands run with the privileges of the hosting Ruby process.
The record
- CVE
- CVE-2019-10780
- Published
- Jan 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- Sylvester Keil
- Product
- BibTeX-Ruby
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=All versions prior to version 5.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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