diff --git a/advisories/github-reviewed/2018/11/GHSA-c2fx-8r76-gh36/GHSA-c2fx-8r76-gh36.json b/advisories/github-reviewed/2018/11/GHSA-c2fx-8r76-gh36/GHSA-c2fx-8r76-gh36.json
index 7adfba5ae89..e0d3ebac2fa 100644
--- a/advisories/github-reviewed/2018/11/GHSA-c2fx-8r76-gh36/GHSA-c2fx-8r76-gh36.json
+++ b/advisories/github-reviewed/2018/11/GHSA-c2fx-8r76-gh36/GHSA-c2fx-8r76-gh36.json
@@ -81,9 +81,7 @@
}
],
"database_specific": {
- "cwe_ids": [
-
- ],
+ "cwe_ids": [],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2020-06-16T21:29:59Z",
diff --git a/advisories/github-reviewed/2019/02/GHSA-fvxv-9xxr-h7wj/GHSA-fvxv-9xxr-h7wj.json b/advisories/github-reviewed/2019/02/GHSA-fvxv-9xxr-h7wj/GHSA-fvxv-9xxr-h7wj.json
index d504f6f1bbc..479cac02cbe 100644
--- a/advisories/github-reviewed/2019/02/GHSA-fvxv-9xxr-h7wj/GHSA-fvxv-9xxr-h7wj.json
+++ b/advisories/github-reviewed/2019/02/GHSA-fvxv-9xxr-h7wj/GHSA-fvxv-9xxr-h7wj.json
@@ -93,9 +93,7 @@
}
],
"database_specific": {
- "cwe_ids": [
-
- ],
+ "cwe_ids": [],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2020-06-16T21:35:31Z",
diff --git a/advisories/github-reviewed/2022/01/GHSA-cjg2-2fjg-fph4/GHSA-cjg2-2fjg-fph4.json b/advisories/github-reviewed/2022/01/GHSA-cjg2-2fjg-fph4/GHSA-cjg2-2fjg-fph4.json
index 293c802c40e..555fae4d5db 100644
--- a/advisories/github-reviewed/2022/01/GHSA-cjg2-2fjg-fph4/GHSA-cjg2-2fjg-fph4.json
+++ b/advisories/github-reviewed/2022/01/GHSA-cjg2-2fjg-fph4/GHSA-cjg2-2fjg-fph4.json
@@ -8,9 +8,7 @@
],
"summary": "Integer underflow in Frontier",
"details": "### Impact\n\nA bug in Frontier's MODEXP precompile implementation can cause an integer underflow in certain conditions. This will cause a node crash for debug builds. For release builds (and production WebAssembly binaries), the impact is limited as it can only cause a normal EVM out-of-gas. It is recommended that you apply the patch as soon as possible.\n\nIf you do not use MODEXP precompile in your runtime, then you are not impacted.\n\n### Patches\n\nPatches are applied in PR #549.\n\n### Workarounds\n\nNone.\n\n### References\n\nPatch PR: #549\n\n### Credits\n\nThanks to SR-Labs for discovering the security vulnerability, and thanks to PureStake team for the patches.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in the [Frontier repo](https://github.com/paritytech/frontier)\n",
- "severity": [
-
- ],
+ "severity": [],
"affected": [
{
"package": {
diff --git a/advisories/github-reviewed/2022/05/GHSA-3v28-9jjp-4g5w/GHSA-3v28-9jjp-4g5w.json b/advisories/github-reviewed/2022/05/GHSA-3v28-9jjp-4g5w/GHSA-3v28-9jjp-4g5w.json
index 01fd7afb29a..c88bbe828fd 100644
--- a/advisories/github-reviewed/2022/05/GHSA-3v28-9jjp-4g5w/GHSA-3v28-9jjp-4g5w.json
+++ b/advisories/github-reviewed/2022/05/GHSA-3v28-9jjp-4g5w/GHSA-3v28-9jjp-4g5w.json
@@ -94,9 +94,7 @@
}
],
"database_specific": {
- "cwe_ids": [
-
- ],
+ "cwe_ids": [],
"severity": "CRITICAL",
"github_reviewed": true,
"github_reviewed_at": "2024-05-01T10:51:17Z",
diff --git a/advisories/github-reviewed/2022/05/GHSA-pwpq-632g-h49g/GHSA-pwpq-632g-h49g.json b/advisories/github-reviewed/2022/05/GHSA-pwpq-632g-h49g/GHSA-pwpq-632g-h49g.json
index bcc22428b94..4fe4d6976e7 100644
--- a/advisories/github-reviewed/2022/05/GHSA-pwpq-632g-h49g/GHSA-pwpq-632g-h49g.json
+++ b/advisories/github-reviewed/2022/05/GHSA-pwpq-632g-h49g/GHSA-pwpq-632g-h49g.json
@@ -108,9 +108,7 @@
}
],
"database_specific": {
- "cwe_ids": [
-
- ],
+ "cwe_ids": [],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2024-04-29T16:41:53Z",
diff --git a/advisories/github-reviewed/2024/10/GHSA-593m-55hh-j8gv/GHSA-593m-55hh-j8gv.json b/advisories/github-reviewed/2024/10/GHSA-593m-55hh-j8gv/GHSA-593m-55hh-j8gv.json
index 9fefd2f191c..9318795c705 100644
--- a/advisories/github-reviewed/2024/10/GHSA-593m-55hh-j8gv/GHSA-593m-55hh-j8gv.json
+++ b/advisories/github-reviewed/2024/10/GHSA-593m-55hh-j8gv/GHSA-593m-55hh-j8gv.json
@@ -3,9 +3,7 @@
"id": "GHSA-593m-55hh-j8gv",
"modified": "2024-10-04T16:32:02Z",
"published": "2024-10-03T18:26:53Z",
- "aliases": [
-
- ],
+ "aliases": [],
"summary": "Sentry SDK Prototype Pollution gadget in JavaScript SDKs",
"details": "### Impact\nIn case a Prototype Pollution vulnerability is present in a user's application or bundled libraries, the Sentry SDK could potentially serve as a gadget to exploit that vulnerability. The exploitability depends on the specific details of the underlying Prototype Pollution issue.\n\n> [!NOTE]\n> This advisory does not indicate the presence of a Prototype Pollution within the Sentry SDK itself. Users are strongly advised to first address any Prototype Pollution vulnerabilities in their application, as they pose a more critical security risk.\n\n### Patches\nThe issue was patched in all Sentry JavaScript SDKs starting from the [8.33.0](https://github.com/getsentry/sentry-javascript/releases/tag/8.33.0) version.\nAlso, the fix was backported to SDK v7 in [7.119.1](https://github.com/getsentry/sentry-javascript/releases/tag/7.119.1).\n\n### References\n* [Prototype Pollution](https://portswigger.net/web-security/prototype-pollution)\n* [Prototype Pollution gadgets](https://portswigger.net/web-security/prototype-pollution#prototype-pollution-gadgets)\n* [sentry-javascript#13838](https://github.com/getsentry/sentry-javascript/pull/13838)",
"severity": [
diff --git a/advisories/github-reviewed/2024/10/GHSA-5rxp-2rhr-qwqv/GHSA-5rxp-2rhr-qwqv.json b/advisories/github-reviewed/2024/10/GHSA-5rxp-2rhr-qwqv/GHSA-5rxp-2rhr-qwqv.json
index 04d55e78e0e..c730b7062ff 100644
--- a/advisories/github-reviewed/2024/10/GHSA-5rxp-2rhr-qwqv/GHSA-5rxp-2rhr-qwqv.json
+++ b/advisories/github-reviewed/2024/10/GHSA-5rxp-2rhr-qwqv/GHSA-5rxp-2rhr-qwqv.json
@@ -3,9 +3,7 @@
"id": "GHSA-5rxp-2rhr-qwqv",
"modified": "2024-10-14T20:55:49Z",
"published": "2024-10-14T20:55:49Z",
- "aliases": [
-
- ],
+ "aliases": [],
"summary": "Session fixation in Elytron SAML adapters",
"details": "A session fixation issue was discovered in the SAML adapters provided by Keycloak. The session ID and JSESSIONID cookie are not changed at login time, even when the turnOffChangeSessionIdOnLogin option is configured. This flaw allows an attacker who hijacks the current session before authentication to trigger session fixation.",
"severity": [
diff --git a/advisories/github-reviewed/2024/10/GHSA-pxg6-pf52-xh8x/GHSA-pxg6-pf52-xh8x.json b/advisories/github-reviewed/2024/10/GHSA-pxg6-pf52-xh8x/GHSA-pxg6-pf52-xh8x.json
index 7bbee59a29b..8d084f31a21 100644
--- a/advisories/github-reviewed/2024/10/GHSA-pxg6-pf52-xh8x/GHSA-pxg6-pf52-xh8x.json
+++ b/advisories/github-reviewed/2024/10/GHSA-pxg6-pf52-xh8x/GHSA-pxg6-pf52-xh8x.json
@@ -8,9 +8,7 @@
],
"summary": "cookie accepts cookie name, path, and domain with out of bounds characters",
"details": "### Impact\n\nThe cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. For example, `serialize(\"userName=; Max-Age=2592000; a\", value)` would result in `\"userName=; Max-Age=2592000; a=test\"`, setting `userName` cookie to `