diff --git a/advisories/github-reviewed/2023/01/GHSA-4jrm-c32x-w4jf/GHSA-4jrm-c32x-w4jf.json b/advisories/github-reviewed/2023/01/GHSA-4jrm-c32x-w4jf/GHSA-4jrm-c32x-w4jf.json index 13156c38110..f19333d8ed7 100644 --- a/advisories/github-reviewed/2023/01/GHSA-4jrm-c32x-w4jf/GHSA-4jrm-c32x-w4jf.json +++ b/advisories/github-reviewed/2023/01/GHSA-4jrm-c32x-w4jf/GHSA-4jrm-c32x-w4jf.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-4jrm-c32x-w4jf", - "modified": "2023-02-09T17:41:49Z", + "modified": "2024-11-26T18:58:52Z", "published": "2023-01-10T21:50:00Z", "aliases": [ "CVE-2023-0163" @@ -12,6 +12,10 @@ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H" + }, + { + "type": "CVSS_V4", + "score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P" } ], "affected": [ @@ -40,6 +44,14 @@ "type": "WEB", "url": "https://github.com/mozilla/node-convict/security/advisories/GHSA-4jrm-c32x-w4jf" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-0163" + }, + { + "type": "WEB", + "url": "https://github.com/mozilla/node-convict/issues/410" + }, { "type": "WEB", "url": "https://github.com/mozilla/node-convict/commit/fb602fbe1e9f14f2e88ecb8179d0f76466d21ecb" @@ -51,11 +63,11 @@ ], "database_specific": { "cwe_ids": [ - + "CWE-1321" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2023-01-10T21:50:00Z", - "nvd_published_at": null + "nvd_published_at": "2024-11-26T12:15:17Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2024/11/GHSA-ffp2-8p2h-4m5j/GHSA-ffp2-8p2h-4m5j.json b/advisories/github-reviewed/2024/11/GHSA-ffp2-8p2h-4m5j/GHSA-ffp2-8p2h-4m5j.json index 721a317ea48..8dc1d8ac6fc 100644 --- a/advisories/github-reviewed/2024/11/GHSA-ffp2-8p2h-4m5j/GHSA-ffp2-8p2h-4m5j.json +++ b/advisories/github-reviewed/2024/11/GHSA-ffp2-8p2h-4m5j/GHSA-ffp2-8p2h-4m5j.json @@ -1,17 +1,21 @@ { "schema_version": "1.4.0", "id": "GHSA-ffp2-8p2h-4m5j", - "modified": "2024-11-22T20:49:20Z", + "modified": "2024-11-26T18:59:48Z", "published": "2024-11-20T18:24:28Z", "aliases": [ "CVE-2024-52796" ], "summary": "Password Pusher rate limiter can be bypassed by forging proxy headers", - "details": "### Impact\n\nPassword Pusher comes with a configurable rate limiter. In versions prior to [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0), the rate limiter could be bypassed by forging proxy headers allowing bad actors to send unlimited traffic to the site potentially causing a denial of service.\n\n\n### Patches\n\nIn [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0), a fix was implemented to only authorize proxies on local IPs which resolves this issue.\n\nIf you are running a remote proxy, please see [this documentation](https://docs.pwpush.com/docs/proxies/#trusted-proxies) on how to authorize the IP address of your remote proxy.\n\n### Workarounds\n\nIt is highly suggested to upgrade to at least [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0) to mitigate this risk.\n\nIf for some reason you cannot immediately upgrade, the alternative is that you can add rules to your proxy and/or firewall to not accept external proxy headers such as `X-Forwarded-*` from clients.\n\n### References\n\nThe new settings are [configurable to authorize remote proxies](https://docs.pwpush.com/docs/proxies/#trusted-proxies).\n", + "details": "### Impact\n\nPassword Pusher comes with a configurable rate limiter. In versions prior to [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0), the rate limiter could be bypassed by forging proxy headers allowing bad actors to send unlimited traffic to the site potentially causing a denial of service.\n\nAdditionally, with the ability to bypass rate limiting, it also allows attackers to more easily execute brute force attacks.\n\n### Patches\n\nIn [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0), a fix was implemented to only authorize proxies on local IPs which resolves this issue.\n\nIf you are running a remote proxy, please see [this documentation](https://docs.pwpush.com/docs/proxies/#trusted-proxies) on how to authorize the IP address of your remote proxy.\n\n### Workarounds\n\nIt is highly suggested to upgrade to at least [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0) to mitigate this risk.\n\nIf for some reason you cannot immediately upgrade, the alternative is that you can add rules to your proxy and/or firewall to not accept external proxy headers such as `X-Forwarded-*` from clients.\n\n### References\n\nThe new settings are [configurable to authorize remote proxies](https://docs.pwpush.com/docs/proxies/#trusted-proxies).\n\n### Credits\n\nThank you to [Positive Technologies](https://www.ptsecurity.com/ww-en/) for reporting and working with me to bring this CVE to the community with the associated fix.\n", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L" + }, + { + "type": "CVSS_V4", + "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U" } ], "affected": [ @@ -65,7 +69,7 @@ "cwe_ids": [ "CWE-770" ], - "severity": "MODERATE", + "severity": "LOW", "github_reviewed": true, "github_reviewed_at": "2024-11-20T18:24:28Z", "nvd_published_at": "2024-11-20T17:15:20Z"