swagger-typescript-api vulnerable to authorization-token exfiltration via spec `$ref`
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| acacode | swagger-typescript-api | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Acacode | Swagger-typescript-api |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-h754-fxp7-88wx | swagger-typescript-api vulnerable to authorization-token exfiltration via spec `$ref` |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.309% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Acacode
Acacode swagger-typescript-api |
|
| Vendors & Products |
Acacode
Acacode swagger-typescript-api |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | swagger-typescript-api generates API clients for Fetch or Axios from OpenAPI specifications. Prior to 13.12.2, src/resolved-swagger-schema.ts getRemoteRequestHeaders forwards --authorizationToken to every URL fetched by fetchRemoteSchemaDocument while warmUpRemoteSchemasCache resolves external $ref URLs, allowing an attacker-controlled OpenAPI spec to exfiltrate the developer or CI bearer token to a cross-origin endpoint. This issue is fixed in version 13.12.2. | |
| Title | swagger-typescript-api vulnerable to authorization-token exfiltration via spec `$ref` | |
| Weaknesses | CWE-200 CWE-201 CWE-522 CWE-918 |
|
| References |
|
|
| Metrics |
cvssV3_1
|