GHSA-M42H-MH85-4QGC
Vulnerability from github – Published: 2019-03-13 17:28 – Updated: 2023-07-05 20:28Possible 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
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 5.2.2.0"
},
"package": {
"ecosystem": "RubyGems",
"name": "railties"
},
"ranges": [
{
"events": [
{
"introduced": "5.2.0"
},
{
"fixed": "5.2.2.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2019-5420"
],
"database_specific": {
"cwe_ids": [
"CWE-330",
"CWE-77"
],
"github_reviewed": true,
"github_reviewed_at": "2020-06-16T21:44:46Z",
"nvd_published_at": "2019-03-27T14:29:00Z",
"severity": "CRITICAL"
},
"details": "# Possible Remote Code Execution Exploit in Rails Development Mode\n\nImpact \n------ \nWith 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. \n\nAll users running an affected release should either upgrade or use one of the workarounds immediately. \n\nReleases \n-------- \nThe 6.0.0.beta3 and 5.2.2.1 releases are available at the normal locations. \n\nWorkarounds \n----------- \nThis issue can be mitigated by specifying a secret key in development mode. \nIn \"config/environments/development.rb\" add this: \n\n```\n config.secret_key_base = SecureRandom.hex(64) \n```\n\nPlease 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. \n\nCredits \n------- \nThanks to ooooooo_q \n",
"id": "GHSA-m42h-mh85-4qgc",
"modified": "2023-07-05T20:28:26Z",
"published": "2019-03-13T17:28:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-5420"
},
{
"type": "WEB",
"url": "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/railties/CVE-2019-5420.yml"
},
{
"type": "WEB",
"url": "https://groups.google.com/forum/#!topic/rubyonrails-security/IsQKvDqZdKw"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Y43636TH4D6T46IC6N2RQVJTRFJAAYGA"
},
{
"type": "WEB",
"url": "https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/46785"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/152704/Ruby-On-Rails-DoubleTap-Development-Mode-secret_key_base-Remote-Code-Execution.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Use of Insufficiently Random Values in Railties Allows Remote Code Execution"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.