Nest Fastify HEAD Request Middleware 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 | ||||||
|---|---|---|---|---|---|---|---|---|---|
| nestjs | nest | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Nestjs | Nest |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wf42-42fg-fg84 | Nest Fastify HEAD Request Middleware Bypass |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.360% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:nestjs:nest:*:*:*:*:*:node.js:*:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nestjs
Nestjs nest |
|
| Vendors & Products |
Nestjs
Nestjs nest |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Nest is a framework for building scalable Node.js server-side applications. In versions 11.1.15 and below, a NestJS application using @nestjs/platform-fastify GET middleware can be bypassed because Fastify automatically redirects HEAD requests to the corresponding GET handlers (if they exist). As a result: middleware will be completely skipped, the HTTP response won't include a body (since the response is truncated when redirecting a HEAD request to a GET handler), and the actual handler will still be executed. This issue is fixed in version 11.1.16. | |
| Title | Nest Fastify HEAD Request Middleware Bypass | |
| Weaknesses | CWE-670 | |
| References |
| |
| Metrics |
cvssV4_0
|