CVE-2022-24797: GO-2022-0413 - Exposure of Sensitive Information in Pomerium in github.com/pomerium/pomerium

CVE-2022-24797 · Severity: low · CVSS 3.1 · Published 2024-08-21

Exposure of Sensitive Information in Pomerium in github.com/pomerium/pomerium

Technologies: github.com/pomerium/pomerium (Go). Vendors: Go.

Quick answers

Is CVE-2022-24797 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-24797 being exploited in the wild.
How severe is CVE-2022-24797?
Low severity, with a CVSS score of 3.1, published 21 August 2024.
Which products and versions are affected?
github.com/pomerium/pomerium (Go) SEMVER:introduced=0.16.0,fixed=0.17.1.
Is there a fix for CVE-2022-24797?
Yes. github.com/pomerium/pomerium (Go): upgrade to 0.17.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-24797?
Check whether you run github.com/pomerium/pomerium (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/pomerium/pomerium (Go): upgrade to 0.17.1 or later
    go get github.com/pomerium/pomerium@v0.17.1

Affected products

  • github.com/pomerium/pomerium (Go) SEMVER:introduced=0.16.0,fixed=0.17.1

Identifiers

  • CVE-2022-24797
  • GHSA-q98f-2x4p-prjr
  • GO-2022-0413

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.