Arbitrary File Overwrite via Symlink Following in dool project
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| scottchiefbaker | dool | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Scottchiefbaker | Dool |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.187% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Dool in versions up to 1.3.8 is vulnerable to symlink following when the "--devel" flag is used, as the application opens a log file without the "O_NOFOLLOW" flag. A local attacker can exploit this by creating a symlink at the expected log file path pointing to a sensitive file, causing dool to truncate and overwrite the target file with log data, which is especially impactful if dool is run with elevated privileges. The issue was addressed by pull request #116 | |
| Title | Arbitrary File Overwrite via Symlink Following in dool project | |
| First Time appeared |
Scottchiefbaker
Scottchiefbaker dool |
|
| Weaknesses | CWE-59 | |
| CPEs | cpe:2.3:a:scottchiefbaker:dool:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Scottchiefbaker
Scottchiefbaker dool |
|
| References |
| |
| Metrics |
cvssV4_0
|