PT-2024-32675 · Pomerium+1 · Pomerium+1
Published
2024-10-02
·
Updated
2024-11-05
·
CVE-2024-47616
CVSS v4.0
7.6
High
| Vector | AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
Name of the Vulnerable Software and Affected Versions
Pomerium versions prior to 0.27.1
Description
Pomerium is an identity and context-aware access proxy. The Pomerium databroker service manages 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. 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, and the core Pomerium databroker gRPC API is not otherwise secured by network access controls.
Recommendations
To resolve the issue, upgrade to Pomerium version 0.27.1 or later.
As a temporary workaround, consider restricting access to the Pomerium internal gRPC API by configuring your network firewall or security groups to limit access to trusted sources only.
For Pomerium Zero deployments only, you can disable the gRPC API listener by setting
grpc address: "" in your YAML configuration file.Exploit
Fix
Incorrect Authorization
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Pomerium
Suse