You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was checking this HackerOne report with a $29000 bounty and I found it very interesting. This is different than Zip Slip. In case of Zip Slip we can inject .. in the file path so we can extract our file in a wrong place. In this report, the attacker crafts a malicious symlink to /etc/passwd when the backend extracts it untar_zxf function only changes the permissions and extract the symlink as is, so the attacker was able to read the passwd file!
I believe we need to add this technique to the WSTG!
The text was updated successfully, but these errors were encountered:
I was checking this HackerOne report with a $29000 bounty and I found it very interesting. This is different than Zip Slip. In case of Zip Slip we can inject
..
in the file path so we can extract our file in a wrong place. In this report, the attacker crafts a malicious symlink to/etc/passwd
when the backend extracts ituntar_zxf
function only changes the permissions and extract the symlink as is, so the attacker was able to read thepasswd
file!I believe we need to add this technique to the WSTG!
The text was updated successfully, but these errors were encountered: