oRPC: Vary Header Injection in CORS Plugin leading to potential Cache/CORS 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 | ||||||
|---|---|---|---|---|---|---|---|---|---|
| middleapi | orpc | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Middleapi | Orpc |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-j9v4-rhgr-4m5f | oRPC: Vary Header Injection in CORS Plugin leading to potential Cache/CORS Bypass |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.543% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Middleapi
Middleapi orpc |
|
| Vendors & Products |
Middleapi
Middleapi orpc |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | oRPC is an tool that helps build APIs that are end-to-end type-safe and adhere to OpenAPI standards. Prior to 1.14.8, the @orpc/server CORS plugin in packages/server/src/plugins/cors.ts copies a client's incoming Vary request header into the response instead of controlling Vary as a response-only header and using Origin for request-origin variation. In deployments behind a shared cache, CDN, or reverse proxy that keys responses using Vary, a client can inject arbitrary variation values, pollute cache keys, and cause inconsistent CORS enforcement for other clients. Default non-cached configurations have no established direct confidentiality, integrity, or availability impact. This issue is fixed in version 1.14.8. | |
| Title | oRPC: Vary Header Injection in CORS Plugin leading to potential Cache/CORS Bypass | |
| Weaknesses | CWE-113 | |
| References |
|
|
| Metrics |
cvssV4_0
|