cve.bz

CVE-2019-5420 Use of Insufficiently Random Values

9.8 criticalExploitEPSS 89%Fix available

Critical (9.8). EPSS 89% estimated probability of exploitation activity in the next 30 days. Fixed in railties 5.2.2.1.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
89% (unchanged from 89% a week ago; 89% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-330 Use of Insufficiently Random Values
CWE-77 Improper Neutralization of Special Elements used in a Command
OWASP Top 10
A04:2025 Cryptographic Failures, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-5420 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-5420?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-5420?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-5420 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
rubyonrails:railsbefore 5.2.2.1
rubyonrails:rails6.0.0:beta1
rubyonrails:rails6.0.0:beta2
debian:debian_linux8.0
fedoraproject:fedora30

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m42h-mh85-4qgcRubyGemsrailties>=5.2.0 <5.2.2.15.2.2.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14rails2:5.2.2.1+dfsg-1DEBIAN-CVE-2019-5420
SUSELinux Enterprise High Performance Computing 15-ESPOS, Linux Enterprise High Performance Computing 15-LTSS, Linux Enterprise Server 15-LTSS and 1 morermt-server2.6.5-3.34.1SUSE-SU-2020:3147-1
SUSELinux Enterprise Module for Public Cloud 15 SP1, Linux Enterprise Module for Server Applications 15 SP1rmt-server2.6.5-3.18.1SUSE-SU-2020:3160-1
SUSELinux Enterprise Module for Public Cloud 15 SP2, Linux Enterprise Module for Server Applications 15 SP2rmt-server2.6.5-3.3.1SUSE-SU-2020:3036-1
openSUSELeap 15.1rmt-server2.6.5-lp151.2.18.2openSUSE-SU-2020:2000-1
openSUSELeap 15.2rmt-server2.6.5-lp152.2.3.1openSUSE-SU-2020:1993-1
openSUSETumbleweedrmt-server2.6.13-1.1openSUSE-SU-2024:10589-1

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This issue did not affect the versions of rh-ror42-rubygem-rails and rh-ror50-rubygem-rails as shipped with Red Hat Software Collections.

ProductPackageStateAdvisory
Red Hat Software Collectionsrh-ror42-rubygem-railsNot affected
Red Hat Software Collectionsrh-ror50-rubygem-railsNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-5420.

Public exploits

Attack patterns (CAPEC)

  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-485 Signature Spoofing by Key Recreation Likelihood: Low · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-40 Manipulating Writeable Terminal Devices Likelihood: High · Severity: Very High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-136 LDAP Injection Likelihood: High · Severity: High
  • CAPEC-183 IMAP/SMTP Command Injection Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-77.

References

Check your stackJSON