diff --git a/advisories/github-reviewed/2024/05/GHSA-4qqq-9vqf-3h3f/GHSA-4qqq-9vqf-3h3f.json b/advisories/github-reviewed/2024/05/GHSA-4qqq-9vqf-3h3f/GHSA-4qqq-9vqf-3h3f.json
index 0c97ce2db71..f27671c36fe 100644
--- a/advisories/github-reviewed/2024/05/GHSA-4qqq-9vqf-3h3f/GHSA-4qqq-9vqf-3h3f.json
+++ b/advisories/github-reviewed/2024/05/GHSA-4qqq-9vqf-3h3f/GHSA-4qqq-9vqf-3h3f.json
@@ -1,10 +1,10 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-4qqq-9vqf-3h3f",
-  "modified": "2024-05-14T20:14:33Z",
+  "modified": "2024-05-20T20:22:55Z",
   "published": "2024-05-14T20:14:33Z",
   "aliases": [
-
+    "CVE-2024-1968"
   ],
   "summary": "Scrapy leaks the authorization header on same-domain but cross-origin redirects",
   "details": "### Impact\n\nSince version 2.11.1, Scrapy drops the `Authorization` header when a request is redirected to a different domain. However, it keeps the header if the domain remains the same but the scheme (http/https) or the port change, all scenarios where the header should also be dropped.\n\nIn the context of a man-in-the-middle attack, this could be used to get access to the value of that `Authorization` header\n\n### Patches\n\nUpgrade to Scrapy 2.11.2.\n\n### Workarounds\n\nThere is no easy workaround for unpatched versions of Scrapy. You can replace the built-in redirect middlewares with custom ones patched for this issue, but you have to patch them yourself, manually.\n\n### References\n\nThis security issue was reported and fixed by @szarny at https://huntr.com/bounties/27f6a021-a891-446a-ada5-0226d619dd1a/.\n",
@@ -47,6 +47,10 @@
     {
       "type": "PACKAGE",
       "url": "https://github.com/scrapy/scrapy"
+    },
+    {
+      "type": "WEB",
+      "url": "https://huntr.com/bounties/27f6a021-a891-446a-ada5-0226d619dd1a"
     }
   ],
   "database_specific": {