This affects Presto server installations. This does NOT affect clients such as the CLI or JDBC driver.
Authenticated users can bypass authorization checks by directly accessing internal APIs. This impacts Presto server installations with secure internal communication configured.
This does not affect installations that have not configured secure internal communication, as these installations are inherently insecure.
This issue has been fixed starting with PrestoSQL version 337.
This issue can be mitigated by blocking network access to internal APIs on the coordinator and workers.
See the Presto documentation for Secure Internal Communication.
If you have any questions or comments about this advisory: * Join the #security channel on Slack. * Contact the security team at security@trino.io
{ "nvd_published_at": "2020-06-30T17:15:00Z", "github_reviewed_at": "2020-06-30T16:33:11Z", "severity": "HIGH", "github_reviewed": true, "cwe_ids": [ "CWE-285" ] }