actix-files before 0.6.10 Information Disclosure via Files
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| actix | actix-files | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Actix | Actix-web |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.539% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | actix-web before 0.6.10 Information Disclosure via Files | actix-files before 0.6.10 Information Disclosure via Files |
| First Time appeared |
Actix actix-files
|
|
| CPEs | cpe:2.3:a:actix:actix-files:*:*:*:*:*:rust:*:* | |
| Vendors & Products |
Actix actix-files
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The actix-files crate (actix_files) before version 0.6.10 contains an information exposure vulnerability. When a non-existing folder is passed as the serve_from argument to Files::new(), the mount path defaults to an empty path; the service then joins the request path with this empty path and canonicalizes it, causing Rust to resolve it as a relative path. As a result, an attacker can request paths that resolve relative to the application's working directory and access unintended files. | |
| Title | actix-web before 0.6.10 Information Disclosure via Files | |
| First Time appeared |
Actix
Actix actix-web |
|
| Weaknesses | CWE-22 | |
| CPEs | cpe:2.3:a:actix:actix-web:*:*:*:*:*:rust:*:* | |
| Vendors & Products |
Actix
Actix actix-web |
|
| References |
| |
| Metrics |
cvssV4_0
|