CVE-2019-13354 json
strong_password Ruby gem malicious version causing Remote Code Execution vulnerability
published 2019-07-08 7 y ago modified 2026-06-17 4 mo ago also GHSA-5h5r-ffc4-c455 , EUVD-2019-0578
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.3%
- EPSS 3.3% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
The strong_password gem 0.0.7 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party. The current version, without this backdoor, is 0.0.6.
Patch / fix
- rubygems strong_password 0.0.8
Exploit prediction
3.33% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | strong_password | >=0.0.7, <0.0.8 |
0.0.8 |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
rubygems.org
/gems/strong_password/versions
web, release-notes, third-party-advisory
-
github.com
/bdmac/strong_password/releases
web, release-notes, third-party-advisory
-
withatwist.dev
/strong-password-rubygem-hijacked.html
web, third-party-advisory
-
benjamin-bouchet.com
/blog/vulnerabilite-dans-la-gem-strong_password-0-0-7/
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-13354
advisory
-
benjamin-bouchet.com
/blog/vulnerabilite-dans-la-gem-strong_password-0-0-7
web
-
github.com
/bdmac/strong_password
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/strong_password/CVE-2019-13354.yml
web
Sources
- CVE List CVE-2019-13354
- GitHub Advisory GHSA-5h5r-ffc4-c455
- NVD CVE-2019-13354
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.