Separate CVE for related symlink vulnerability? #41
Description
This CVE seems only to talk about maliciously crafted destination paths, and not maliciously crafted symlinks. Is there a separate CVE for that?
For example, I could extract a symlink evilEntry.txt => ../../../../etc/password to ./evilEntry.txt and then the next entry in the archive could be again evilEntry.txt, but this time as a file with the contents PWNed!, which would overwrite /etc/password.