Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Is this really a 7-zip issue, or is it a Microsoft issue? #5

Open
JudgeDreddKLC opened this issue Apr 18, 2022 · 3 comments
Open

Is this really a 7-zip issue, or is it a Microsoft issue? #5

JudgeDreddKLC opened this issue Apr 18, 2022 · 3 comments

Comments

@JudgeDreddKLC
Copy link

The mitigation steps don't quite make sense to me, because if someone really wanted to exploit this, they would just have to download the affected 7zip executable, the affected chm file, and the specifically crafted 7z file to any system, and voila. So that means there really is no mitigation to this other than, maybe, application blacklisting?

Am I missing something?

Expanding on the above, that means it would be far easier for someone to create a malicious dll file that explots the inherent vulnerability in Microsoft's CHM system, and then you have an exploit that doesn't depend on 7zip at all. This means that the vulnerability isn't really with 7zip at all, but with Microsoft, and there is no type of mitigation until Microsoft patches it.

@kagancapar
Copy link
Owner

actually there is an API call authorization problem here, not just on hh.exe. Our example is via the hh.exe file.

@brlin-tw
Copy link

API call authorization problem

Elaborate on the exact 7-Zip code that contains this problem.

@kagancapar
Copy link
Owner

The mitigation steps don't quite make sense to me, because if someone really wanted to exploit this, they would just have to download the affected 7zip executable, the affected chm file, and the specifically crafted 7z file to any system, and voila. So that means there really is no mitigation to this other than, maybe, application blacklisting?

Am I missing something?

Expanding on the above, that means it would be far easier for someone to create a malicious dll file that explots the inherent vulnerability in Microsoft's CHM system, and then you have an exploit that doesn't depend on 7zip at all. This means that the vulnerability isn't really with 7zip at all, but with Microsoft, and there is no type of mitigation until Microsoft patches it.

You are close to the solution. :)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants