diff --git a/advisories/github-reviewed/2019/03/GHSA-m42h-mh85-4qgc/GHSA-m42h-mh85-4qgc.json b/advisories/github-reviewed/2019/03/GHSA-m42h-mh85-4qgc/GHSA-m42h-mh85-4qgc.json
index 17271c97dd1..dbae7c955fa 100644
--- a/advisories/github-reviewed/2019/03/GHSA-m42h-mh85-4qgc/GHSA-m42h-mh85-4qgc.json
+++ b/advisories/github-reviewed/2019/03/GHSA-m42h-mh85-4qgc/GHSA-m42h-mh85-4qgc.json
@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-m42h-mh85-4qgc",
-  "modified": "2023-01-26T21:08:19Z",
+  "modified": "2023-07-05T20:28:26Z",
   "published": "2019-03-13T17:28:35Z",
   "aliases": [
     "CVE-2019-5420"
   ],
-  "summary": "Use of Insufficiently Random Values in railties",
-  "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 \nguess the automatically generated development mode secret token.  This secret \ntoken can be used in combination with other Rails internals to escalate to a \nremote code execution exploit. \n\nAll users running an affected release should either upgrade or use one of the \nworkarounds 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 \nat present. Users of earlier unsupported releases are advised to upgrade as \nsoon as possible as we cannot guarantee the continued availability of security \nfixes for unsupported releases. \n\nCredits \n------- \nThanks to ooooooo_q \n",
+  "summary": "Use of Insufficiently Random Values in Railties Allows Remote Code Execution",
+  "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",
   "severity": [
     {
       "type": "CVSS_V3",