Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-r7rh-jww5-5fjr
No affected components available
Impact
We've identified a vulnerability in the Pomerium databroker service API that may grant unintended access under specific conditions. This affects only certain Pomerium Zero and Pomerium Enterprise deployments.
Who is affected?
A Pomerium deployment is susceptible to this issue if all of the following conditions are met:
- You have issued a service account access token using Pomerium Zero or Pomerium Enterprise.
- The access token has an explicit expiration date in the future.
- The core Pomerium databroker gRPC API is not otherwise secured by network access controls.
If your deployment does not meet all of these conditions, you are not affected by this vulnerability.
Details
The Pomerium databroker service is responsible for managing all persistent Pomerium application state. Requests to the databroker service API are authorized by the presence of a JSON Web Token (JWT) signed by a key known by all Pomerium services in the same deployment. However, incomplete validation of this JWT meant that some service account access tokens would incorrectly be treated as valid for the purpose of databroker API authorization.
Improper access to the databroker API could allow exfiltration of user info, spoofing of user sessions, or tampering with Pomerium routes, policies, and other settings.
Discovery
This issue was discovered during internal review. At this time we have no evidence to suggest that this vulnerability has been exploited in the wild.
Patches
We have released Pomerium v0.27.1 which includes a fix for the JWT validation logic. All affected users are strongly encouraged to upgrade to this version.
Workarounds
If you cannot upgrade immediately, consider the following mitigations:
-
Network access controls: Restrict access to the Pomerium internal gRPC API by configuring your network firewall or security groups to limit access to trusted sources only. Ensure that the port specified in the
grpc_addresssetting is not exposed to unauthorized networks. -
For Pomerium Zero deployments only: As of Pomerium v0.26.0, you can disable the gRPC API listener by setting
grpc_address: ""in your YAML configuration file. In all-in-one mode, Pomerium does not require the internal gRPC API to be exposed beyond localhost.
For more information
If you have questions or need further assistance:
- Open an issue in the pomerium/pomerium repository.
- Contact us at security@pomerium.com.
The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard