Caleb Doxsey

3 exploits Active since Mar 2022
CVE-2022-24797 WRITEUP MEDIUM WRITEUP
Pomerium 0.16.0-0.17.0 - Unauthenticated Exposure of Sensitive Information via Debug and Metrics Endpoints
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.
CVSS 6.5
CVE-2023-33189 WRITEUP CRITICAL WRITEUP
Pomerium < 0.17.4, 0.18.0-0.18.0, 0.19.0-0.19.1, 0.20.0, 0.21.0-0.21.3, 0.22.0-0.22.1 - Improper Authorization
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.
CVSS 10.0
CVE-2024-39315 WRITEUP MEDIUM WRITEUP
Pomerium < 0.26.1 - Unintended OAuth2 Token Exposure via User Info Page
Pomerium is an identity and context-aware access proxy. Prior to version 0.26.1, the Pomerium user info page (at `/.pomerium`) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens are not intended to be exposed to end users. This issue may be more severe in the presence of a cross-site scripting vulnerability in an upstream application proxied through Pomerium. If an attacker could insert a malicious script onto a web page proxied through Pomerium, that script could access these tokens by making a request to the `/.pomerium` endpoint. Upstream applications that authenticate only the ID token may be vulnerable to user impersonation using a token obtained in this manner. Note that an OAuth2 access token or ID token by itself is not sufficient to hijack a user's Pomerium session. Upstream applications should not be vulnerable to user impersonation via these tokens provided the application verifies the Pomerium JWT for each request, the connection between Pomerium and the application is secured by mTLS, or the connection between Pomerium and the application is otherwise secured at the network layer. The issue is patched in Pomerium v0.26.1. No known workarounds are available.
CVSS 5.7