Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-82mm-ffjr-h86c

MEDIUMFix: istio/istio@4c73414

GHSA-82mm-ffjr-h86c is a medium-severity (CVSS 6.8) vulnerability in istio.io/istio. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-82mm-ffjr-h86c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Authorization bypass in Istio

Also known asCVE-2020-16844
Published
Feb 15, 2022
Updated
Nov 8, 2023
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known

Real-World Exposure

2 pkgs affected
🐹istio.io/istio🐹istio.io/istio

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

In Istio 1.5.0 though 1.5.8 and Istio 1.6.0 through 1.6.7, when users specify an AuthorizationPolicy resource with DENY actions using wildcard suffixes (e.g. *-some-suffix) for source principals or namespace fields, callers will never be denied access, bypassing the intended policy.

Specific Go Packages Affected

istio.io/istio/pilot/pkg/security/authz/model/matcher

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Goistio.io/istio1.5.0&&< 1.5.91.5.9
🐹Goistio.io/istio1.6.0&&< 1.6.81.6.8
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for istio.io/istio. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update istio.io/istio to 1.5.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-82mm-ffjr-h86c is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-82mm-ffjr-h86c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-82mm-ffjr-h86c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Istio 1.5.0 though 1.5.8 and Istio 1.6.0 through 1.6.7, when users specify an AuthorizationPolicy resource with DENY actions using wildcard suffixes (e.g. *-some-suffix) for source principals or namespace fields, callers will never be denied access, bypassing the intended policy. ### Specific Go Packages Affected istio.io/istio/pilot/pkg/security/authz/model/matcher
O3 Security · Impact-Aware SCA

Is GHSA-82mm-ffjr-h86c in your dependencies?

O3 detects GHSA-82mm-ffjr-h86c across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.