# CVE-2023-33189: Incorrect Authorization with specially crafted requests > Attackers can bypass authorization controls in Pomerium using specially crafted requests, gaining unauthorized access to protected resources. - **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 May 2023 - **Updated:** 10 Jan 2025 - **Also known as:** GHSA-pvrc-wvj2-f59p, GO-2023-1800 ## What is CVE-2023-33189? CVE-2023-33189 is a critical missing authorization vulnerability in pomerium, published on 30 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Pomerium is an identity and context-aware access proxy. With specially crafted requests, incorrect authorization decisions may be made by Pomerium. This issue has been patched in versions 0.17.4, 0.18.1, 0.19.2, 0.20.1, 0.21.4 and 0.22.2. Weakness: CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2023-33189? 13 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 | All versions | 0.17.4, 0.18.1, 0.19.2, 0.20.1, 0.21.4, 0.22.2 | | `github.com/pomerium/pomerium` | Go | All versions | 0.17.4 | | `github.com/pomerium/pomerium` | Go | All versions | 0.17.4 | | `github.com/pomerium/pomerium` | Go | From 0.18.0 | 0.18.1 | | `github.com/pomerium/pomerium` | Go | From 0.18.0 | 0.18.1 | | `github.com/pomerium/pomerium` | Go | From 0.19.0 | 0.19.2 | | `github.com/pomerium/pomerium` | Go | From 0.19.0 | 0.19.2 | | `github.com/pomerium/pomerium` | Go | From 0.20.0 | 0.20.1 | | `github.com/pomerium/pomerium` | Go | From 0.20.0 | 0.20.1 | | `github.com/pomerium/pomerium` | Go | From 0.21.0 | 0.21.4 | | `github.com/pomerium/pomerium` | Go | From 0.21.0 | 0.21.4 | | `github.com/pomerium/pomerium` | Go | From 0.22.0 | 0.22.2 | | `github.com/pomerium/pomerium` | Go | From 0.22.0 | 0.22.2 | Products: Pomerium Pomerium. ## How do I fix CVE-2023-33189? Upgrade github.com/pomerium/pomerium to a fixed version for your release line: 0.17.4, 0.18.1, 0.19.2 or 0.20.1. ## Is CVE-2023-33189 being exploited? There is no known exploitation of CVE-2023-33189 in the wild and no public exploit code. ## Other vulnerabilities in pomerium - [CVE-2022-24797](https://insights.sbomify.com/CVE-2022-24797/): Exposure of Sensitive Information in Pomerium (medium 6.5) - [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-2023-33189 and fix it if it is affected. What it is: CVE-2023-33189 is a critical missing authorization vulnerability in pomerium, published on 30 May 2023. 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-2023-33189 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/pomerium/pomerium (Go): affected all versions; fixed in 0.17.4, 0.18.1, 0.19.2, 0.20.1, 0.21.4, 0.22.2 - github.com/pomerium/pomerium (Go): affected all versions; fixed in 0.17.4 - github.com/pomerium/pomerium (Go): affected all versions; fixed in 0.17.4 - github.com/pomerium/pomerium (Go): affected from 0.18.0; fixed in 0.18.1 - github.com/pomerium/pomerium (Go): affected from 0.18.0; fixed in 0.18.1 - github.com/pomerium/pomerium (Go): affected from 0.19.0; fixed in 0.19.2 - github.com/pomerium/pomerium (Go): affected from 0.19.0; fixed in 0.19.2 - github.com/pomerium/pomerium (Go): affected from 0.20.0; fixed in 0.20.1 - github.com/pomerium/pomerium (Go): affected from 0.20.0; fixed in 0.20.1 - github.com/pomerium/pomerium (Go): affected from 0.21.0; fixed in 0.21.4 - github.com/pomerium/pomerium (Go): affected from 0.21.0; fixed in 0.21.4 - github.com/pomerium/pomerium (Go): affected from 0.22.0; fixed in 0.22.2 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-2023-33189/ (Markdown: https://insights.sbomify.com/CVE-2023-33189/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-33189 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-33189 - OSV: https://osv.dev/vulnerability/CVE-2023-33189 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-33189/ Summaries are generated and may contain mistakes; the official description above is the record.