# CVE-2022-24797: Exposure of Sensitive Information in Pomerium

> Attackers can access debug and metrics endpoints in distributed mode to leak sensitive environment data or cause denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Mar 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-q98f-2x4p-prjr, GO-2022-0413

## What is CVE-2022-24797?

CVE-2022-24797 is a medium-severity vulnerability in pomerium, published on 31 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pomerium is an identity-aware access proxy. In distributed service mode, Pomerium's Authenticate service exposes pprof debug and prometheus metrics handlers to untrusted traffic. This can leak potentially sensitive environmental information or lead to limited denial of service conditions. This issue is patched in version v0.17.1 Workarounds: Block access to `/debug` and `/metrics` paths on the authenticate service. This can be done with any L7 proxy, including Pomerium's own proxy service.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-24797?

3 open source packages ship an affected version, including github.com/pomerium/pomerium. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/pomerium/pomerium` | Go | From 0.16.0 | 0.17.1 |
| `github.com/pomerium/pomerium` | Go | From 0.16.0 | 0.17.1 |
| `github.com/pomerium/pomerium` | Go | From 0.16.0 | 0.17.1 |

Products: Pomerium Pomerium.

## How do I fix CVE-2022-24797?

Upgrade github.com/pomerium/pomerium to 0.17.1 or later.

## Is CVE-2022-24797 being exploited?

There is no known exploitation of CVE-2022-24797 in the wild and no public exploit code.

## Other vulnerabilities in pomerium

- [CVE-2023-33189](https://insights.sbomify.com/CVE-2023-33189/): Incorrect Authorization with specially crafted requests (critical 10.0)
- [CVE-2021-29651](https://insights.sbomify.com/CVE-2021-29651/): JWT leak via Open Redirect in Programmatic access (medium 6.1)
- [CVE-2021-29652](https://insights.sbomify.com/CVE-2021-29652/): pomerium_signature is not verified in middleware in github.com/pomerium/pomerium (medium 6.1)
- [CVE-2024-39315](https://insights.sbomify.com/CVE-2024-39315/): Pomerium exposed OAuth2 access and ID tokens in user info endpoint response (medium 5.7)
- [CVE-2021-41230](https://insights.sbomify.com/CVE-2021-41230/): OIDC claims not updated from Identity Provider in Pomerium (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24797 and fix it if it is affected.

What it is: CVE-2022-24797 is a medium-severity vulnerability in pomerium, published on 31 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24797 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/pomerium/pomerium (Go): affected from 0.16.0; fixed in 0.17.1
- github.com/pomerium/pomerium (Go): affected from 0.16.0; fixed in 0.17.1
- github.com/pomerium/pomerium (Go): affected from 0.16.0; fixed in 0.17.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24797/ (Markdown: https://insights.sbomify.com/CVE-2022-24797/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24797
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24797
- OSV: https://osv.dev/vulnerability/CVE-2022-24797

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24797/
Summaries are generated and may contain mistakes; the official description above is the record.