HighGHSA-64rh-r86q-75ffCVE-2020-1764GO-2022-0631

Hard coded cryptographic key in Kiali

Published 18 May 2021 · Updated 21 Aug 2024

Is your project on an affected github.com/kiali/kiali?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.15.1
Fixed in
1.15.1
Update to the fixed version for your release line, for example:go get github.com/kiali/kiali@v1.15.1

Details

A hard-coded cryptographic key vulnerability in the default configuration file was found in Kiali, all versions prior to 1.15.1. A remote attacker could abuse this flaw by creating their own JWT signed tokens and bypass Kiali authentication mechanisms, possibly gaining privileges to view and alter the Istio configuration.

Is GHSA-64rh-r86q-75ff in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/kiali/kiali, and gives you the command that fixes it.

More advisories for github.com/kiali/kiali

  • LowCVE-2021-3495Access control flaw in Kiali in github.com/kiali/kiali · 21 Aug 2024
  • LowCVE-2021-20278Kiali Authentication Bypass vulnerability in github.com/kiali/kiali · 21 Aug 2024
  • LowCVE-2020-1762Insufficient Session Expiration in Kiali in github.com/kiali/kiali · 21 Aug 2024
  • LowCVE-2022-3962Kiali content spoofing vulnerability in github.com/kiali/kiali · 21 Aug 2024
  • MediumCVE-2022-3962Kiali content spoofing vulnerability · 23 Sept 2023
  • HighCVE-2021-3495Access control flaw in Kiali · 8 Jun 2021
All 9 advisories for github.com/kiali/kiali

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.