parsedmarc 9.0.6 < 11.0.1 Path Traversal via Forensic Report Subject
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| domainaware | parsedmarc | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Domainaware | Parsedmarc |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.429% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Domainaware
Domainaware parsedmarc |
|
| Vendors & Products |
Domainaware
Domainaware parsedmarc |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | parsedmarc 9.0.6 before 11.0.1 writes forensic report sample files using an output path derived from the email subject. When the subject consists entirely of path traversal sequences, the filename sanitization function produces an empty string, and a fallback to the raw unsanitized subject causes the resulting file to be written outside the intended samples directory. An attacker who can cause a forensic failure report with a crafted Subject to be processed can write a dot-prefixed file with attacker-controlled content to an ancestor directory of the configured samples output path. Exploitation requires that file output for forensic report samples is enabled. | |
| Title | parsedmarc 9.0.6 < 11.0.1 Path Traversal via Forensic Report Subject | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|