CVE-2019-10780 json
BibTeX-Ruby vulnerable to OS command injection
published 2020-01-22 6 y ago modified 2026-09-10 1 mo ago also GHSA-c5r5-7pfh-6qg6 , EUVD-2020-0299
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
BibTeX-ruby before 5.1.0 allows shell command injection due to unsanitized user input being passed directly to the built-in Ruby Kernel.open method through BibTeX.open.
Patch / fix
- rubygems bibtex-ruby 5.1.0
- bibtex-ruby_project bibtex-ruby 5.1.0
Exploit prediction
2.81% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- snyk.io https://snyk.io/vuln/SNYK-RUBY-BIBTEXRUBY-542602 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | bibtex-ruby | <5.1.0 |
5.1.0 |
Affected products
- n/a BibTeX-ruby
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
snyk.io
/vuln/SNYK-RUBY-BIBTEXRUBY-542602
web, exploit, patch, third-party-advisory
-
github.com
/inukshuk/bibtex-ruby/commit/14406f4460f4e1ecabd25ca94f809b3ea7c5fb11
web
-
nvd.nist.gov
/vuln/detail/CVE-2019-10780
advisory
-
github.com
/advisories/GHSA-c5r5-7pfh-6qg6
advisory
-
github.com
/inukshuk/bibtex-ruby
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/bibtex-ruby/CVE-2019-10780.yml
web
Sources
- CVE List CVE-2019-10780
- GitHub Advisory GHSA-c5r5-7pfh-6qg6
- NVD CVE-2019-10780
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.