Security readout for executives and security teams
Plain-English summary
Presto server versions before 337 can let a user bypass intended authorization by reaching internal APIs directly. The business concern is unauthorized access to sensitive query or platform data where vulnerable servers expose those APIs. The issue is fixed in 337, and network controls around internal APIs are an explicit mitigation.
Executive priority
Prioritize remediation for production Presto clusters handling sensitive data, especially where user networks can reach coordinator or worker internal APIs. Upgrade or isolate promptly, but do not assume internet-wide exploitation from the provided evidence.
Technical view
CVE-2020-15087 is CWE-285 improper authorization in Presto server. Sources state authenticated users can bypass authorization checks by directly accessing internal APIs. It affects Presto server installations before version 337 with secure internal communication configured, not CLI or JDBC clients.
Likely exposure
Exposure is likely limited to Presto server deployments below version 337 where secure internal communication is configured and coordinator or worker internal APIs are network-reachable by users or untrusted systems.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. The described attack requires access to internal Presto APIs; details sufficient for weaponization are not included here.
Researcher notes
The affected condition is narrow: Presto server before 337 with secure internal communication configured. Sources also note installations without secure internal communication are inherently insecure but not affected by this specific flaw. No exploit proof, payload, or active campaign evidence is provided.
Mitigation direction
- Upgrade affected Presto server installations to version 337 or later.
- Block network access to internal APIs on coordinators and workers.
- Restrict Presto server management and worker networks to trusted infrastructure.
- Review the GitHub advisory and release notes before production changes.
- Do not treat CLI or JDBC clients as affected products.
Validation and detection
- Inventory all Presto server versions and flag any below 337.
- Confirm whether secure internal communication is configured on each server deployment.
- Review firewall and segmentation rules protecting coordinator and worker internal APIs.
- Verify exposed services from user and application network zones.
- Confirm remediation by documenting upgraded versions or blocked internal API access.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-285: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-15087 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N2.84Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/prestosql/presto/security/advisories/GHSA-f6pc-crhh-cp96CVE reference · x_refsource_CONFIRM
- https://trino.io/docs/current/release/release-337.html#security-changesCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.