@hapi/inert: Static-file confinement bypass via sibling-prefix path
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| hapijs | inert | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Hapi | Inert |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-rcvq-m9j9-6f4g | @hapi/inert has a static-file confinement bypass via sibling-prefix path |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.590% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hapi
Hapi inert |
|
| Vendors & Products |
Hapi
Hapi inert |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | @hapi/inert provides static file and directory handlers for hapi.js. From 4.0.0 to 7.1.0, @hapi/inert serves static files from a directory configured with path in the directory or file handlers or relativeTo for h.file(), with confinement enforced by the confine option, but the confinement check compared the resolved absolute path against the confine directory using a raw string-prefix test, so a sibling directory such as /app/static-secret next to /app/static was incorrectly accepted and could allow an unauthenticated remote attacker to read files via /..%2fstatic-secret/secret.txt. This issue is fixed in version 7.1.1. | |
| Title | @hapi/inert: Static-file confinement bypass via sibling-prefix path | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|