diff --git a/advisories/github-reviewed/2024/01/GHSA-5h86-8mv2-jq9f/GHSA-5h86-8mv2-jq9f.json b/advisories/github-reviewed/2024/01/GHSA-5h86-8mv2-jq9f/GHSA-5h86-8mv2-jq9f.json index c4d070ff7ca..a2534550660 100644 --- a/advisories/github-reviewed/2024/01/GHSA-5h86-8mv2-jq9f/GHSA-5h86-8mv2-jq9f.json +++ b/advisories/github-reviewed/2024/01/GHSA-5h86-8mv2-jq9f/GHSA-5h86-8mv2-jq9f.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-5h86-8mv2-jq9f", - "modified": "2024-01-29T22:31:03Z", + "modified": "2024-01-30T16:12:20Z", "published": "2024-01-29T22:31:03Z", "aliases": [ "CVE-2024-23334" @@ -9,7 +9,10 @@ "summary": "aiohttp is vulnerable to directory traversal", "details": "### Summary\nImproperly configuring static resource resolution in aiohttp when used as a web server can result in the unauthorized reading of arbitrary files on the system.\n\n### Details\nWhen using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option 'follow_symlinks' can be used to determine whether to follow symbolic links outside the static root directory. When 'follow_symlinks' is set to True, there is no validation to check if a given file path is within the root directory.This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present.\n\ni.e. An application is only vulnerable with setup code like:\n```\napp.router.add_routes([\n web.static(\"/static\", \"static/\", follow_symlinks=True), # Remove follow_symlinks to avoid the vulnerability\n])\n```\n\n### Impact\nThis is a directory traversal vulnerability with CWE ID 22. When using aiohttp as a web server and enabling static resource resolution with `follow_symlinks` set to True, it can lead to this vulnerability. This vulnerability has been present since the introduction of the `follow_symlinks` parameter.\n\n### Workaround\nEven if upgrading to a patched version of aiohttp, we recommend following these steps regardless.\n\nIf using `follow_symlinks=True` outside of a restricted local development environment, disable the option immediately. This option is NOT needed to follow symlinks which point to a location _within_ the static root directory, it is _only_ intended to allow a symlink to break out of the static directory. Even with this CVE fixed, there is still a substantial risk of misconfiguration when using this option on a server that accepts requests from remote users.\n\nAdditionally, aiohttp has always recommended using a reverse proxy server (such as nginx) to handle static resources and _not_ to use these static resources in aiohttp for production environments. Doing so also protects against this vulnerability, and is why we expect the number of affected users to be very low.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/pull/8079/files", "severity": [ - + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N" + } ], "affected": [ { @@ -37,6 +40,14 @@ "type": "WEB", "url": "https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5h86-8mv2-jq9f" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-23334" + }, + { + "type": "WEB", + "url": "https://github.com/aio-libs/aiohttp/pull/8079" + }, { "type": "WEB", "url": "https://github.com/aio-libs/aiohttp/pull/8079/files" @@ -57,6 +68,6 @@ "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2024-01-29T22:31:03Z", - "nvd_published_at": null + "nvd_published_at": "2024-01-29T23:15:08Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2024/01/GHSA-8qpw-xqxj-h4r2/GHSA-8qpw-xqxj-h4r2.json b/advisories/github-reviewed/2024/01/GHSA-8qpw-xqxj-h4r2/GHSA-8qpw-xqxj-h4r2.json index b50d58579d7..2e457c2c58f 100644 --- a/advisories/github-reviewed/2024/01/GHSA-8qpw-xqxj-h4r2/GHSA-8qpw-xqxj-h4r2.json +++ b/advisories/github-reviewed/2024/01/GHSA-8qpw-xqxj-h4r2/GHSA-8qpw-xqxj-h4r2.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-8qpw-xqxj-h4r2", - "modified": "2024-01-29T22:30:07Z", + "modified": "2024-01-30T16:11:56Z", "published": "2024-01-29T22:30:07Z", "aliases": [ "CVE-2024-23829" @@ -9,7 +9,10 @@ "summary": "aiohttp's HTTP parser (the python one, not llhttp) still overly lenient about separators", "details": "### Summary\nSecurity-sensitive parts of the *Python HTTP parser* retained minor differences in allowable character sets, that must trigger error handling to robustly match frame boundaries of proxies in order to protect against injection of additional requests. Additionally, validation could trigger exceptions that were not handled consistently with processing of other malformed input.\n\n### Details\nThese problems are rooted in pattern matching protocol elements, previously improved by PR #3235 and GHSA-gfw2-4jvh-wgfg:\n\n1. The expression `HTTP/(\\d).(\\d)` lacked another backslash to clarify that the separator should be a literal dot, not just *any* Unicode code point (result: `HTTP/(\\d)\\.(\\d)`).\n\n2. The HTTP version was permitting Unicode digits, where only ASCII digits are standards-compliant.\n\n3. Distinct regular expressions for validating HTTP Method and Header field names were used - though both should (at least) apply the common restrictions of rfc9110 `token`.\n\n### PoC\n`GET / HTTP/1รถ1`\n`GET / HTTP/1.๐Ÿ™`\n`GET/: HTTP/1.1`\n`Content-Encoding?: chunked`\n\n### Impact\nPrimarily concerns running an aiohttp server without llhttp:\n 1. **behind a proxy**: Being more lenient than internet standards require could, depending on deployment environment, assist in request smuggling.\n 2. **directly accessible** or exposed behind proxies relaying malformed input: the unhandled exception could cause excessive resource consumption on the application server and/or its logging facilities.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/pull/8074/files", "severity": [ - + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L" + } ], "affected": [ { @@ -41,10 +44,18 @@ "type": "WEB", "url": "https://github.com/aio-libs/aiohttp/security/advisories/GHSA-gfw2-4jvh-wgfg" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-23829" + }, { "type": "WEB", "url": "https://github.com/aio-libs/aiohttp/pull/3235" }, + { + "type": "WEB", + "url": "https://github.com/aio-libs/aiohttp/pull/8074" + }, { "type": "WEB", "url": "https://github.com/aio-libs/aiohttp/pull/8074/files" @@ -60,11 +71,11 @@ ], "database_specific": { "cwe_ids": [ - + "CWE-444" ], - "severity": "LOW", + "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2024-01-29T22:30:07Z", - "nvd_published_at": null + "nvd_published_at": "2024-01-29T23:15:08Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2024/01/GHSA-v9wr-2xrg-v7w8/GHSA-v9wr-2xrg-v7w8.json b/advisories/github-reviewed/2024/01/GHSA-v9wr-2xrg-v7w8/GHSA-v9wr-2xrg-v7w8.json index b9f1cd47f52..b4478cd8cd6 100644 --- a/advisories/github-reviewed/2024/01/GHSA-v9wr-2xrg-v7w8/GHSA-v9wr-2xrg-v7w8.json +++ b/advisories/github-reviewed/2024/01/GHSA-v9wr-2xrg-v7w8/GHSA-v9wr-2xrg-v7w8.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-v9wr-2xrg-v7w8", - "modified": "2024-01-23T20:11:27Z", + "modified": "2024-01-30T16:11:44Z", "published": "2024-01-23T18:31:11Z", "aliases": [ "CVE-2024-22490" @@ -9,7 +9,10 @@ "summary": "Cross-site Scripting in beetl-bbs", "details": "Cross Site Scripting (XSS) vulnerability in beetl-bbs 2.0 allows attackers to run arbitrary code via the /index keyword parameter.", "severity": [ - + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N" + } ], "affected": [ {