Vulnerability in io.prestosql:presto-server (CVE-2020-15087)
Summary
Vulnerability in io.prestosql:presto-server (CVE-2020-15087). Confidential information can be exposed externally. Mitigation: upgrade to 337 or later.
Original description
The description as published by the source.
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:
- Join the #security channel on Slack.
- Contact the security team at security@trino.io
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-15087 has been found in io.prestosql:presto-server.
Confidential information can be exposed externally.
What to do: upgrade io.prestosql:presto-server to 337 or later.
If unsure, ask your IT team or search "io.prestosql:presto-server CVE-2020-15087" on the vendor's site.
CVE-2020-15087 (io.prestosql:presto-server) — CWE-285
Attack vector: remote (network-reachable) / unauthenticated
Patched: 337 — apply immediately
Workaround: This issue can be mitigated by blocking network access to internal APIs on the coordinator and workers.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) exists in io.prestosql:presto-server.
Check the vendor advisory for the affected versions of io.prestosql:presto-server.
Severity: ?. Confidential information can be exposed externally.
Update to 337.
Workaround: This issue can be mitigated by blocking network access to internal APIs on the coordinator and workers.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.prestosql:presto-server を使っているサービスとバージョンを洗い出す。
-
2Apply temporary workaround mitigate
This issue can be mitigated by blocking network access to internal APIs on the coordinator and workers.パッチが適用されるまでの応急処置として、This issue can be mitigated by blocking network access to internal APIs on the coordinator and workers. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade io.prestosql:presto-server to 337ステージング環境で 337 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web prestosql.io
- web trino.io