CVE-2020-8595

highpriority · track · 30EPSS 0.026 · 85 %ileEURUUS
grimoire priorityP2 · Scheduled
Exploitable?
—
no known exploitation
Likely / severe?
2.61% (85th) EPSS
CVSS 7.5 · high
Is it mine?
10 products
Check your exposure
Who says so?
5 sources
cnnvd · enisa_euvd · fstec_bdu · nvd

EPSS · scored 2026-10-27

Istio versions 1.2.10 (End of Life) and prior, 1.3 through 1.3.7, and 1.4 through 1.4.3 allows authentication bypass. The Authentication Policy exact-path matching logic can allow unauthorized access to HTTP paths even if they are configured to be only accessed after presenting a valid JWT token. For example, an attacker can add a ? or # character to a URI that would otherwise satisfy an exact-path match.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • Fixedservicemesh-proxy-0:1.0.7-1.el8.src as a component of OpenShift Service Mesh 1.0redhat_csaf

    The OpenShift Service Mesh release notes provide information on the features and known issues: https://docs.openshift.com/container-platform/4.3/service_mesh/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2020:0477
  • Fixedservicemesh-proxy-0:1.0.7-1.el8.x86_64 as a component of OpenShift Service Mesh 1.0redhat_csaf

    The OpenShift Service Mesh release notes provide information on the features and known issues: https://docs.openshift.com/container-platform/4.3/service_mesh/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2020:0477
  • Workaroundservicemesh-proxy-0:1.0.7-1.el8.src as a component of OpenShift Service Mesh 1.0redhat_csaf

    Depending on the paths used in the exact match clause, it is possible to update the path to a regex. As provided by the Istio Product Committee, the following mitigation can be employed. The original policy specifying a JWT protected path is as follows: --- apiVersion: "authentication.istio.io/v1alpha1" kind: "Policy" metadata: name: "jwt-example" namespace: istio-system spec: targets: - name: istio-ingressgateway origins: - jwt: issuer: "testing@secure.istio.io" jwksUri: "https://raw.githubusercontent.com/istio/istio/release-1.4/security/tools/jwt/samples/jwks.json" trigger_rules: - included_paths: - exact: /productpage The exact path definition can then be updated to a regular expression: --- - jwt: issuer: "testing@secure.istio.io" jwksUri: "https://raw.githubusercontent.com/istio/istio/release-1.4/security/tools/jwt/samples/jwks.json" trigger_rules: - included_paths: - regex: '/productpage(\?.*)?' - regex: '/productpage(#.*)?'

  • Workaroundservicemesh-proxy-0:1.0.7-1.el8.x86_64 as a component of OpenShift Service Mesh 1.0redhat_csaf

    Depending on the paths used in the exact match clause, it is possible to update the path to a regex. As provided by the Istio Product Committee, the following mitigation can be employed. The original policy specifying a JWT protected path is as follows: --- apiVersion: "authentication.istio.io/v1alpha1" kind: "Policy" metadata: name: "jwt-example" namespace: istio-system spec: targets: - name: istio-ingressgateway origins: - jwt: issuer: "testing@secure.istio.io" jwksUri: "https://raw.githubusercontent.com/istio/istio/release-1.4/security/tools/jwt/samples/jwks.json" trigger_rules: - included_paths: - exact: /productpage The exact path definition can then be updated to a regular expression: --- - jwt: issuer: "testing@secure.istio.io" jwksUri: "https://raw.githubusercontent.com/istio/istio/release-1.4/security/tools/jwt/samples/jwks.json" trigger_rules: - included_paths: - regex: '/productpage(\?.*)?' - regex: '/productpage(#.*)?'

02

cvss

Technical severity, 0–10. One row per scoring source.

7.5
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.7–7.5

v2.07.5highAV:N/AC:L/Au:N/C:P/I:P/A:Pprimary · NVD / NIST USexploitability 10 · impact 6.4
v3.17.3highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Lprimary · NVD / NIST USexploitability 3.9 · impact 3.4
v3.17.3highAV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Lsecondary · FSTEC (BDU) RU
v3.16.7mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:Usecondary · CVSS-BT (t0sche)
v3.17.3highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Lsecondary · Red Hat Product Security US
03

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-287USprimaryCWE-285USCWE-287US
04

affected products (10)

Products and version ranges known to be affected.

05

advisories (1)

Vendor and ecosystem advisories describing this.

  • RHSA-2020:0477Red Hat Security Advisory: Red Hat OpenShift Service Mesh 1.0.7 servicemesh-proxy security update2020-02-12csaf · redhat_csafUS

    Red Hat OpenShift Service Mesh 1.0.7. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

06

also known as (4)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

cnnvdenisa_euvdfstec_bdunvdredhat_csafNVDCVE.orgMITRE
published 2020-02-12modified 2026-06-17
09

references (20)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan