diff --git a/advisories/github-reviewed/2018/07/GHSA-2j9c-9vmv-7m39/GHSA-2j9c-9vmv-7m39.json b/advisories/github-reviewed/2018/07/GHSA-2j9c-9vmv-7m39/GHSA-2j9c-9vmv-7m39.json
index be6afa8cce3..5e2c00ba585 100644
--- a/advisories/github-reviewed/2018/07/GHSA-2j9c-9vmv-7m39/GHSA-2j9c-9vmv-7m39.json
+++ b/advisories/github-reviewed/2018/07/GHSA-2j9c-9vmv-7m39/GHSA-2j9c-9vmv-7m39.json
@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-2j9c-9vmv-7m39",
-  "modified": "2022-04-26T18:19:29Z",
+  "modified": "2023-09-05T21:45:13Z",
   "published": "2018-07-31T18:18:39Z",
   "aliases": [
     "CVE-2017-11173"
   ],
-  "summary": "Missing anchor in Rack-Cors allows malicious third party site to perform CORS request",
-  "details": "Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted example.com domain name and not the malicious example.net domain name, then example.com.example.net (as well as example.com-example.net) would be inadvertently allowed.",
+  "summary": "Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request",
+  "details": "Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted `example.com` domain name and not the malicious `example.net` domain name, then `example.com.example.net` (as well as `example.com-example.net`) would be inadvertently allowed.",
   "severity": [
     {
       "type": "CVSS_V3",
@@ -20,6 +20,11 @@
         "ecosystem": "RubyGems",
         "name": "rack-cors"
       },
+      "ecosystem_specific": {
+        "affected_functions": [
+          ""
+        ]
+      },
       "ranges": [
         {
           "type": "ECOSYSTEM",