Express Gateway through 1.16.11 OAuth 2.0 Refresh Token Validation Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ExpressGateway | express-gateway | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Express-gateway | Express-gateway |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.363% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Express-gateway express-gateway
|
|
| Vendors & Products |
Express-gateway express-gateway
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Express Gateway through 1.16.11 contains an authentication bypass vulnerability in the OAuth 2.0 refresh_token grant that fails to validate the token secret or issuing client. Attackers with any valid client credentials and the identifier portion of another user's refresh token can obtain that user's access token and impersonate them against oauth2-protected APIs. | |
| Title | Express Gateway through 1.16.11 OAuth 2.0 Refresh Token Validation Bypass | |
| First Time appeared |
Express-gateway
Express-gateway express-gateway Docker Image |
|
| Weaknesses | CWE-287 | |
| CPEs | cpe:2.3:a:express-gateway:express-gateway_docker_image:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Express-gateway
Express-gateway express-gateway Docker Image |
|
| References |
|
|
| Metrics |
cvssV3_1
|