Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2021-41130— X-Endpoint-API-UserInfo can be spoofed in cloudendpoints Extensible Service Proxy

Quick assessment

Affected
cloudendpoints esp
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Extensible Service Proxy(ESP)是一种代理,可为 JSON/REST 或 gRPC API 服务启用 API 管理功能。 Extensible Service Proxy 存在安全漏洞,目前尚无此漏洞的相关信息,请随时关注CNNVD或厂商公告。

CVSS 6.4 · Medium EPSS 0.39% · P30
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2021-41130

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
X-Endpoint-API-UserInfo can be spoofed in cloudendpoints Extensible Service Proxy
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
使用欺骗进行的认证绕过
Source: CVE Program / CVE List V5
Vulnerability Title
Extensible Service Proxy 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Extensible Service Proxy(ESP)是一种代理,可为 JSON/REST 或 gRPC API 服务启用 API 管理功能。 Extensible Service Proxy 存在安全漏洞,目前尚无此漏洞的相关信息,请随时关注CNNVD或厂商公告。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
cloudendpoints esp < 1.58.0 -

II. Public POCs for CVE-2021-41130

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2021-41130

请登录查看更多情报信息。

Patches & Fixes for CVE-2021-41130 (1)

Vendor Advisories for CVE-2021-41130 (1)

Other References for CVE-2021-41130 (2)

IV. Related Vulnerabilities

V. Comments for CVE-2021-41130

No comments yet


Leave a comment