nnn through 5.3 Symlink-Following Write via NNN_FIFO Handling
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| jarun | nnn | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Jarun | Nnn |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.116% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jarun
Jarun nnn |
|
| Vendors & Products |
Jarun
Jarun nnn |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | nnn through 5.3 contains an insecure file handling vulnerability that allows local attackers to redirect writes because main() accepts an existing NNN_FIFO path without verifying it is a FIFO. Attackers can pre-create the documented predictable /tmp/nnn.fifo path as a symlink or readable regular file, causing victim-writable files to be overwritten or leaking the victim's browsed paths. | |
| Title | nnn through 5.3 Symlink-Following Write via NNN_FIFO Handling | |
| Weaknesses | CWE-59 | |
| References |
|
|
| Metrics |
cvssV3_1
|