# CVE-2023-33189: GO-2023-1800 - Pomerium vulnerable to Incorrect Authorization with specially crafted requests in github.com/pomerium/pomerium

Source: https://junglewise.ai/threats/cve-2023-33189-pomerium-vulnerable-to-incorrect-authorization-with-specially  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-08-20  
License: CC BY 4.0 with a link back

CVE-2023-33189 · Severity: low · CVSS 3.1 · Published 2024-08-20

Pomerium vulnerable to Incorrect Authorization with specially crafted requests in github.com/pomerium/pomerium

Technologies: [github.com/pomerium/pomerium (Go)](https://junglewise.ai/threats/technologies/github-com-pomerium-pomerium). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2023-33189 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2023-33189 being exploited in the wild.

**How severe is CVE-2023-33189?** Low severity, with a CVSS score of 3.1, published 20 August 2024.

**Which products and versions are affected?** github.com/pomerium/pomerium (Go) SEMVER:introduced=0,fixed=0.17.4,introduced=0.18.0,fixed=0.18.1,introduced=0.19.0,fixed=0.19.2,introduced=0.20.0,fixed=0.20.1,introduced=0.21.0,fixed=0.21.4,introduced=0.22.0,fixed=0.22.2, SEMVER:introduced=0.22.0,fixed=0.22.2.

**Is there a fix for CVE-2023-33189?** Yes. github.com/pomerium/pomerium (Go): upgrade to 0.22.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2023-33189?** 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.22.2 or later

  ```sh
  go get github.com/pomerium/pomerium@v0.22.2
  ```


## Affected products

- github.com/pomerium/pomerium (Go) SEMVER:introduced=0,fixed=0.17.4,introduced=0.18.0,fixed=0.18.1,introduced=0.19.0,fixed=0.19.2,introduced=0.20.0,fixed=0.20.1,introduced=0.21.0,fixed=0.21.4,introduced=0.22.0,fixed=0.22.2, SEMVER:introduced=0.22.0,fixed=0.22.2

## Identifiers

- CVE-2023-33189
- GHSA-pvrc-wvj2-f59p
- GO-2023-1800

## Related threats

- [Pomerium uncontrolled resource consumption in HPKE callback decompression](https://junglewise.ai/threats/cve-2026-50285-pomerium-uncontrolled-resource-consumption-in-hpke-callback)
- [Pomerium service account access token may grant unintended access to databroker API](https://junglewise.ai/threats/cve-2024-47616-pomerium-service-account-access-token-may-grant-unintended-access)
- [GO-2022-0933 - Incorrect handling of H2 GOAWAY + SETTINGS frames in github.com/pomerium/pomerium](https://junglewise.ai/threats/cve-2021-39162-incorrect-handling-of-h2-goaway-settings-frames)
- [GO-2022-0827 - pomerium_signature is not verified in middleware in github.com/pomerium/pomerium](https://junglewise.ai/threats/cve-2021-29652-pomerium-signature-is-not-verified-in-middleware-in-github-com)
- [GO-2022-0783 - JWT leak via Open Redirect in Programmatic access in github.com/pomerium/pomerium](https://junglewise.ai/threats/cve-2021-29651-jwt-leak-via-open-redirect-in-programmatic-access)