ArchiveTar through 1.4.10 has ://
filename sanitization only to address phar attacks, and thus any other stream-wrapper attack (such as file://
to overwrite files) can still succeed. See: https://github.com/pear/ArchiveTar/issues/33
{ "nvd_published_at": "2020-11-19T19:15:00Z", "cwe_ids": [ "CWE-74" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2021-03-23T00:20:31Z" }