Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

multiple heap-use-after-frees in decompile.c #130

Closed
traceprobe opened this issue Mar 22, 2018 · 3 comments
Closed

multiple heap-use-after-frees in decompile.c #130

traceprobe opened this issue Mar 22, 2018 · 3 comments

Comments

@traceprobe
Copy link

traceprobe commented Mar 22, 2018

In latest release version (0.4.8) of libming, there are multiple heap-use-after frees in decompileGETVARIABLE/decompileSingleArgBuiltInFunctionCall/decompilePUSHPARAM/decompileDELETE/decompileSETTARGET/decompileSUBSTRING/decompileNEWOBJECT functions of decompile.c, which could be triggered by the POCs below.

To reproduce the issue, compile with ASAN and run: ./swftophp $POC

libming_poc.zip

@hlef
Copy link
Contributor

hlef commented May 14, 2018

None of these reproducible with latest master, all duplicates of former issues.

Please, do not request CVE numbers before checking reproducibility and similarity with earlier / fixed in master issues.

@hlef
Copy link
Contributor

hlef commented May 14, 2018

FTR, this was fixed in 3a000c7.

@traceprobe
Copy link
Author

Thanks for your comments. And I double-checked this issue.

While this issue is still reproducible in the latest release version (0.4.8 released on Apr. 7 2017), it's already fixed in earlier commits (3a000c7) when the author is trying to fix several heap-overflows, even before such issue is created. I would check out the latest commit if I encounter any problem with libming.

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

No branches or pull requests

3 participants