{"containers": {"cna": {"affected": [{"product": "esp", "vendor": "cloudendpoints", "versions": [{"status": "affected", "version": "< 1.58.0"}]}], "descriptions": [{"lang": "en", "value": "Extensible Service Proxy, a.k.a. ESP is a proxy which enables API management capabilities for JSON/REST or gRPC API services. ESPv1 can be configured to authenticate a JWT token. Its verified JWT claim is passed to the application by HTTP header \"X-Endpoint-API-UserInfo\", the application can use it to do authorization. But if there are two \"X-Endpoint-API-UserInfo\" headers from the client, ESPv1 only replaces the first one, the 2nd one will be passed to the application. An attacker can send two \"X-Endpoint-API-UserInfo\" headers, the second one with a fake JWT claim. Application may use the fake JWT claim to do the authorization. This impacts following ESPv1 usages: 1) Users have configured ESPv1 to do JWT authentication with Google ID Token as described in the referenced google endpoint document. 2) Users backend application is using the info in the \"X-Endpoint-API-UserInfo\" header to do the authorization. It has been fixed by v1.58.0. You need to patch it in the following ways: * If your docker image is using tag \":1\", needs to re-start the container to pick up the new version. The tag \":1\" will automatically point to the latest version. * If your docker image tag pings to a specific minor version, e.g. \":1.57\". You need to update it to \":1.58\" and re-start the container. There are no workaround for this issue."}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.4, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "LOW", "scope": "CHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N", "version": "3.1"}}], "problemTypes": [{"descriptions": [{"cweId": "CWE-290", "description": "CWE-290: Authentication Bypass by Spoofing", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"dateUpdated": "2021-10-07T18:30:17", "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M"}, "references": [{"tags": ["x_refsource_CONFIRM"], "url": "https://github.com/cloudendpoints/esp/security/advisories/GHSA-43wx-8qmj-9r9q"}, {"tags": ["x_refsource_MISC"], "url": "https://github.com/cloudendpoints/esp/commit/e310c4f91d229a072507f80c73811489b4cdff27"}, {"tags": ["x_refsource_MISC"], "url": "https://cloud.google.com/endpoints/docs/openapi/authenticating-users-google-id"}, {"tags": ["x_refsource_MISC"], "url": "https://github.com/cloudendpoints/esp/releases/tag/v1.58.0"}], "source": {"advisory": "GHSA-43wx-8qmj-9r9q", "discovery": "UNKNOWN"}, "title": "X-Endpoint-API-UserInfo can be spoofed in cloudendpoints Extensible Service Proxy", "x_legacyV4Record": {"CVE_data_meta": {"ASSIGNER": "security-advisories@github.com", "ID": "CVE-2021-41130", "STATE": "PUBLIC", "TITLE": "X-Endpoint-API-UserInfo can be spoofed in cloudendpoints Extensible Service Proxy"}, "affects": {"vendor": {"vendor_data": [{"product": {"product_data": [{"product_name": "esp", "version": {"version_data": [{"version_value": "< 1.58.0"}]}}]}, "vendor_name": "cloudendpoints"}]}}, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": {"description_data": [{"lang": "eng", "value": "Extensible Service Proxy, a.k.a. ESP is a proxy which enables API management capabilities for JSON/REST or gRPC API services. ESPv1 can be configured to authenticate a JWT token. Its verified JWT claim is passed to the application by HTTP header \"X-Endpoint-API-UserInfo\", the application can use it to do authorization. But if there are two \"X-Endpoint-API-UserInfo\" headers from the client, ESPv1 only replaces the first one, the 2nd one will be passed to the application. An attacker can send two \"X-Endpoint-API-UserInfo\" headers, the second one with a fake JWT claim. Application may use the fake JWT claim to do the authorization. This impacts following ESPv1 usages: 1) Users have configured ESPv1 to do JWT authentication with Google ID Token as described in the referenced google endpoint document. 2) Users backend application is using the info in the \"X-Endpoint-API-UserInfo\" header to do the authorization. It has been fixed by v1.58.0. You need to patch it in the following ways: * If your docker image is using tag \":1\", needs to re-start the container to pick up the new version. The tag \":1\" will automatically point to the latest version. * If your docker image tag pings to a specific minor version, e.g. \":1.57\". You need to update it to \":1.58\" and re-start the container. There are no workaround for this issue."}]}, "impact": {"cvss": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.4, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "LOW", "scope": "CHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N", "version": "3.1"}}, "problemtype": {"problemtype_data": [{"description": [{"lang": "eng", "value": "CWE-290: Authentication Bypass by Spoofing"}]}]}, "references": {"reference_data": [{"name": "https://github.com/cloudendpoints/esp/security/advisories/GHSA-43wx-8qmj-9r9q", "refsource": "CONFIRM", "url": "https://github.com/cloudendpoints/esp/security/advisories/GHSA-43wx-8qmj-9r9q"}, {"name": "https://github.com/cloudendpoints/esp/commit/e310c4f91d229a072507f80c73811489b4cdff27", "refsource": "MISC", "url": "https://github.com/cloudendpoints/esp/commit/e310c4f91d229a072507f80c73811489b4cdff27"}, {"name": "https://cloud.google.com/endpoints/docs/openapi/authenticating-users-google-id", "refsource": "MISC", "url": "https://cloud.google.com/endpoints/docs/openapi/authenticating-users-google-id"}, {"name": "https://github.com/cloudendpoints/esp/releases/tag/v1.58.0", "refsource": "MISC", "url": "https://github.com/cloudendpoints/esp/releases/tag/v1.58.0"}]}, "source": {"advisory": "GHSA-43wx-8qmj-9r9q", "discovery": "UNKNOWN"}}}, "adp": [{"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-04T02:59:31.599Z"}, "title": "CVE Program Container", "references": [{"tags": ["x_refsource_CONFIRM", "x_transferred"], "url": "https://github.com/cloudendpoints/esp/security/advisories/GHSA-43wx-8qmj-9r9q"}, {"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://github.com/cloudendpoints/esp/commit/e310c4f91d229a072507f80c73811489b4cdff27"}, {"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://cloud.google.com/endpoints/docs/openapi/authenticating-users-google-id"}, {"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://github.com/cloudendpoints/esp/releases/tag/v1.58.0"}]}]}, "cveMetadata": {"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "assignerShortName": "GitHub_M", "cveId": "CVE-2021-41130", "datePublished": "2021-10-07T18:30:17", "dateReserved": "2021-09-15T00:00:00", "dateUpdated": "2024-08-04T02:59:31.599Z", "state": "PUBLISHED"}, "dataType": "CVE_RECORD", "dataVersion": "5.1"}

{}

{"configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:google:extensible_service_proxy:*:*:*:*:*:*:*:*", "matchCriteriaId": "DB5147A5-A760-4866-AA59-9D0463B68A64", "versionEndExcluding": "1.58.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "descriptions": [{"lang": "en", "value": "Extensible Service Proxy, a.k.a. ESP is a proxy which enables API management capabilities for JSON/REST or gRPC API services. ESPv1 can be configured to authenticate a JWT token. Its verified JWT claim is passed to the application by HTTP header \"X-Endpoint-API-UserInfo\", the application can use it to do authorization. But if there are two \"X-Endpoint-API-UserInfo\" headers from the client, ESPv1 only replaces the first one, the 2nd one will be passed to the application. An attacker can send two \"X-Endpoint-API-UserInfo\" headers, the second one with a fake JWT claim. Application may use the fake JWT claim to do the authorization. This impacts following ESPv1 usages: 1) Users have configured ESPv1 to do JWT authentication with Google ID Token as described in the referenced google endpoint document. 2) Users backend application is using the info in the \"X-Endpoint-API-UserInfo\" header to do the authorization. It has been fixed by v1.58.0. You need to patch it in the following ways: * If your docker image is using tag \":1\", needs to re-start the container to pick up the new version. The tag \":1\" will automatically point to the latest version. * If your docker image tag pings to a specific minor version, e.g. \":1.57\". You need to update it to \":1.58\" and re-start the container. There are no workaround for this issue."}, {"lang": "es", "value": "Extensible Service Proxy, tambi\u00e9n se conoce como ESP, es un proxy que permite la administraci\u00f3n de la API para los servicios JSON/REST o gRPC. ESPv1 puede ser configurado para autenticar un token JWT. Su reclamaci\u00f3n JWT verificada se pasa a la aplicaci\u00f3n mediante el encabezado HTTP \"X-Endpoint-API-UserInfo\", la aplicaci\u00f3n puede usarla para hacer la autorizaci\u00f3n. Pero si presenta dos encabezados \"X-Endpoint-API-UserInfo\" del cliente, ESPv1 s\u00f3lo reemplaza la primera, la segunda ser\u00e1 pasada a la aplicaci\u00f3n. Un atacante puede enviar dos encabezados \"X-Endpoint-API-UserInfo\", la segunda con una reclamaci\u00f3n JWT falsa. La aplicaci\u00f3n puede usar la reclamaci\u00f3n JWT falsa para hacer la autorizaci\u00f3n. Esto afecta a los siguientes usos de ESPv1: 1) Los usuarios han configurado ESPv1 para hacer la autenticaci\u00f3n JWT con Google ID Token como se describe en el documento de Google Endpoint referenciado. 2) La aplicaci\u00f3n backend de los usuarios usa la informaci\u00f3n del encabezado \"X-Endpoint-API-UserInfo\" para realizar la autorizaci\u00f3n. Se ha corregido en la versi\u00f3n 1.58.0. Es necesario parchearlo de las siguientes maneras: * Si su imagen docker est\u00e1 usando la etiqueta \":1\", necesita reiniciar el contenedor para recoger la nueva versi\u00f3n. La etiqueta \":1\" apuntar\u00e1 autom\u00e1ticamente a la \u00faltima versi\u00f3n. * Si la etiqueta de su imagen docker apunta a una versi\u00f3n menor espec\u00edfica, por ejemplo \":1.57\". Debe actualizarla a \":1.58\" y reiniciar el contenedor. No se presenta ninguna soluci\u00f3n para este problema"}], "id": "CVE-2021-41130", "lastModified": "2024-11-21T06:25:32.493", "metrics": {"cvssMetricV2": [{"acInsufInfo": false, "baseSeverity": "MEDIUM", "cvssData": {"accessComplexity": "MEDIUM", "accessVector": "NETWORK", "authentication": "SINGLE", "availabilityImpact": "NONE", "baseScore": 4.9, "confidentialityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "vectorString": "AV:N/AC:M/Au:S/C:P/I:P/A:N", "version": "2.0"}, "exploitabilityScore": 6.8, "impactScore": 4.9, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "source": "nvd@nist.gov", "type": "Primary", "userInteractionRequired": false}], "cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.4, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "LOW", "scope": "CHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N", "version": "3.1"}, "exploitabilityScore": 3.1, "impactScore": 2.7, "source": "security-advisories@github.com", "type": "Secondary"}, {"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 5.4, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N", "version": "3.1"}, "exploitabilityScore": 2.8, "impactScore": 2.5, "source": "nvd@nist.gov", "type": "Primary"}]}, "published": "2021-10-07T19:15:08.843", "references": [{"source": "security-advisories@github.com", "tags": ["Vendor Advisory"], "url": "https://cloud.google.com/endpoints/docs/openapi/authenticating-users-google-id"}, {"source": "security-advisories@github.com", "tags": ["Patch", "Third Party Advisory"], "url": "https://github.com/cloudendpoints/esp/commit/e310c4f91d229a072507f80c73811489b4cdff27"}, {"source": "security-advisories@github.com", "tags": ["Third Party Advisory"], "url": "https://github.com/cloudendpoints/esp/releases/tag/v1.58.0"}, {"source": "security-advisories@github.com", "tags": ["Third Party Advisory"], "url": "https://github.com/cloudendpoints/esp/security/advisories/GHSA-43wx-8qmj-9r9q"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Vendor Advisory"], "url": "https://cloud.google.com/endpoints/docs/openapi/authenticating-users-google-id"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Patch", "Third Party Advisory"], "url": "https://github.com/cloudendpoints/esp/commit/e310c4f91d229a072507f80c73811489b4cdff27"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Third Party Advisory"], "url": "https://github.com/cloudendpoints/esp/releases/tag/v1.58.0"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Third Party Advisory"], "url": "https://github.com/cloudendpoints/esp/security/advisories/GHSA-43wx-8qmj-9r9q"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-290"}], "source": "security-advisories@github.com", "type": "Secondary"}, {"description": [{"lang": "en", "value": "CWE-290"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{}