CVE-2019-5420
highpriority · act · 80OT risk · criticalEPSS 0.893 · 100 %ileexploit · weaponizedDEEURUUSEPSS · scored 2026-10-22
A remote code execution vulnerability in development mode Rails <5.2.2.1, <6.0.0.beta3 can allow an attacker to guess the automatically generated development mode secret token. This secret token can be used in combination with other Rails internals to escalate to a remote code execution exploit.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 7.5–9.8
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (14)
Public proof-of-concept and weaponised exploit code.
- AnasTaoutaou/CVE-2019-5420AnasTaoutaou/CVE-2019-5420PoC · poc_in_github
- Eremiel/CVE-2019-5420Eremiel/CVE-2019-5420PoC · poc_in_github
- WildWestCyberSecurity/cve-2019-5420-POCcve-2019-5420 POC simple ruby scriptPoC · poc_in_github
affected products (16)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2025-1467Ruby on Rails: Mehrere SchwachstellenDeutsch2019-03-13csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Ruby on Rails ausnutzen, um Informationen offenzulegen, einen Denial of Service Zustand hervorzurufen oder beliebigen Programmcode auszuführen.
- GHSA-m42h-mh85-4qgcUse of Insufficiently Random Values in Railties Allows Remote Code Execution2019-03-13ghsa · osvUS
# Possible Remote Code Execution Exploit in Rails Development Mode Impact ------ With some knowledge of a target application it is possible for an attacker to guess the automatically generated development mode secret token. This secret token can be used in combination with other Rails internals to escalate to a remote code execution exploit. All users running an affected release should either upgrade or use one of the workarounds immediately. Releases -------- The 6.0.0.beta3 and 5.2.2.1 releases are available at the normal locations. Workarounds ----------- This issue can be mitigated by specifying a secret key in development mode. In "config/environments/development.rb" add this: ``` config.secret_key_base = SecureRandom.hex(64) ``` Please note that only the 5.2.x, 5.1.x, 5.0.x, and 4.2.x series are supported at present. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases. Credits ------- Thanks to ooooooo_q
also known as (4)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (26)
External citations — patches, advisories, analysis.
- http://packetstormsecurity.com/files/152704/Ruby-On-Rails-DoubleTap-Development-Mode-secret_key_base-Remote-Code-Execution.htmlcnnvd
- http://www.ibm.com/support/docview.wsscnnvd
- http://www.ibm.com/support/docview.wss?uid=ibm10881644cnnvd
- http://www.securityfocus.com/bid/107427cnnvd
- https://groups.google.com/forum/#!topic/rubyonrails-security/IsQKvDqZdKwcnnvd
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Y43636TH4D6T46IC6N2RQVJTRFJAAYGA/cnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2019-5420cnnvd
- https://packetstormsecurity.com/files/152704/Ruby-On-Rails-DoubleTap-Development-Mode-secret/key/base-Remote-Code-Execution.htmlcnnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan