Skip to content

Privilege escalation in Presto

High severity GitHub Reviewed Published Jun 29, 2020 in trinodb/trino • Updated Feb 2, 2023

Package

maven io.prestosql:presto-server (Maven)

Affected versions

< 337

Patched versions

337

Description

Affected

This affects Presto server installations. This does NOT affect clients such as the CLI or JDBC driver.

Impact

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.

Patches

This issue has been fixed starting with PrestoSQL version 337.

Workarounds

This issue can be mitigated by blocking network access to internal APIs on the coordinator and workers.

References

See the Presto documentation for Secure Internal Communication.

For more information

If you have any questions or comments about this advisory:

References

@electrum electrum published to trinodb/trino Jun 29, 2020
Reviewed Jun 30, 2020
Published to the GitHub Advisory Database Jun 30, 2020
Published by the National Vulnerability Database Jun 30, 2020
Last updated Feb 2, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

EPSS score

0.104%
(43rd percentile)

Weaknesses

CVE ID

CVE-2020-15087

GHSA ID

GHSA-f6pc-crhh-cp96

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.