CVE-2024-47616

Source
https://nvd.nist.gov/vuln/detail/CVE-2024-47616
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-47616.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2024-47616
Aliases
Related
Published
2024-10-02T22:15:03Z
Modified
2024-10-09T20:59:12.076863Z
Summary
[none]
Details

Pomerium is an identity and context-aware access proxy. 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. 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. This vulnerability is fixed in 0.27.1.

References

Affected packages

Git / github.com/pomerium/pomerium

Affected ranges

Type
GIT
Repo
https://github.com/pomerium/pomerium
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed

Affected versions

v0.*

v0.0.1
v0.0.2
v0.0.3
v0.0.4
v0.0.5
v0.1.0
v0.10.0
v0.10.0-rc1
v0.10.0-rc2
v0.10.0-rc3
v0.11.0
v0.11.0-rc1
v0.11.0-rc2
v0.12.0
v0.14.0
v0.14.0-rc2
v0.15.0
v0.15.6
v0.16.0
v0.17.0
v0.18.0
v0.19.0
v0.2.0
v0.20.0
v0.23.0
v0.25.0
v0.26.0
v0.27.0
v0.3.0
v0.4.0
v0.5.0
v0.6.0
v0.7.0
v0.7.1
v0.7.2
v0.8.0
v0.9.0