cve-2024-47616
Vulnerability from cvelistv5
Published
2024-10-02 21:10
Modified
2024-10-03 15:43
Severity ?
EPSS score ?
Summary
Pomerium's service account access token may grant unintended access to databroker API
References
{ "containers": { "adp": [ { "metrics": [ { "other": { "content": { "id": "CVE-2024-47616", "options": [ { "Exploitation": "none" }, { "Automatable": "no" }, { "Technical Impact": "partial" } ], "role": "CISA Coordinator", "timestamp": "2024-10-03T15:43:18.016372Z", "version": "2.0.3" }, "type": "ssvc" } } ], "providerMetadata": { "dateUpdated": "2024-10-03T15:43:26.879Z", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP" }, "title": "CISA ADP Vulnrichment" } ], "cna": { "affected": [ { "product": "pomerium", "vendor": "pomerium", "versions": [ { "status": "affected", "version": "\u003c 0.27.1" } ] } ], "descriptions": [ { "lang": "en", "value": "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." } ], "metrics": [ { "cvssV3_1": { "attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.8, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N", "version": "3.1" } } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-863", "description": "CWE-863: Incorrect Authorization", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "dateUpdated": "2024-10-02T21:10:24.146Z", "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M" }, "references": [ { "name": "https://github.com/pomerium/pomerium/security/advisories/GHSA-r7rh-jww5-5fjr", "tags": [ "x_refsource_CONFIRM" ], "url": "https://github.com/pomerium/pomerium/security/advisories/GHSA-r7rh-jww5-5fjr" }, { "name": "https://github.com/pomerium/pomerium/commit/e018cf0fc0979d2abe25ff705db019feb7523444", "tags": [ "x_refsource_MISC" ], "url": "https://github.com/pomerium/pomerium/commit/e018cf0fc0979d2abe25ff705db019feb7523444" }, { "name": "https://github.com/pomerium/pomerium/releases/tag/v0.27.1", "tags": [ "x_refsource_MISC" ], "url": "https://github.com/pomerium/pomerium/releases/tag/v0.27.1" } ], "source": { "advisory": "GHSA-r7rh-jww5-5fjr", "discovery": "UNKNOWN" }, "title": "Pomerium\u0027s service account access token may grant unintended access to databroker API" } }, "cveMetadata": { "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "assignerShortName": "GitHub_M", "cveId": "CVE-2024-47616", "datePublished": "2024-10-02T21:10:24.146Z", "dateReserved": "2024-09-27T20:37:22.120Z", "dateUpdated": "2024-10-03T15:43:26.879Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2024-47616\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2024-10-02T22:15:03.010\",\"lastModified\":\"2024-10-04T13:50:43.727\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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.\"},{\"lang\":\"es\",\"value\":\"Pomerium es un proxy de acceso que reconoce la identidad y el contexto. El servicio de agente de datos Pomerium es responsable de administrar todo el estado persistente de la aplicaci\u00f3n Pomerium. Las solicitudes a la API del servicio de agente de datos se autorizan mediante la presencia de un token web JSON (JWT) firmado por una clave conocida por todos los servicios Pomerium en la misma implementaci\u00f3n. Sin embargo, la validaci\u00f3n incompleta de este JWT significaba que algunos tokens de acceso a la cuenta de servicio se tratar\u00edan incorrectamente como v\u00e1lidos para el prop\u00f3sito de la autorizaci\u00f3n de la API del agente de datos. El acceso inadecuado a la API del agente de datos podr\u00eda permitir la exfiltraci\u00f3n de informaci\u00f3n del usuario, la suplantaci\u00f3n de sesiones de usuario o la manipulaci\u00f3n de las rutas, pol\u00edticas y otras configuraciones de Pomerium. Una implementaci\u00f3n de Pomerium es susceptible a este problema si se cumplen todas las siguientes condiciones: ha emitido un token de acceso a la cuenta de servicio mediante Pomerium Zero o Pomerium Enterprise, el token de acceso tiene una fecha de vencimiento expl\u00edcita en el futuro y la API gRPC del agente de datos Pomerium principal no est\u00e1 protegida de otra manera por controles de acceso a la red. Esta vulnerabilidad se corrigi\u00f3 en 0.27.1.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N\",\"baseScore\":6.8,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":1.6,\"impactScore\":5.2}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-863\"}]}],\"references\":[{\"url\":\"https://github.com/pomerium/pomerium/commit/e018cf0fc0979d2abe25ff705db019feb7523444\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/pomerium/pomerium/releases/tag/v0.27.1\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/pomerium/pomerium/security/advisories/GHSA-r7rh-jww5-5fjr\",\"source\":\"security-advisories@github.com\"}]}}" } }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.