-
Notifications
You must be signed in to change notification settings - Fork 424
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
tidy ASAN build global-buffer-overflow bug #443
Comments
@marcograss, thanks for the issue... In the process of setting up a You say this also happens in Will get back soonest... |
@marcograss Can you provide input file that triggers this bug? |
no input at all is required to trigger it, just execute tidy with address sanitizer. |
@marcograss it seem PR #445 fixes this... Appreciate it if you get a chance to apply the patch and test... thanks... |
thanks, I will test as soon as I return back to work, mitre thinks it can be reachable from apps using libtidy, what's your tought about it? they assigned CVE-2016-6583 but I don't have my linux box so I cannot actually check this analysis |
Fix static buffer overrrun (issue #443)
@marcograss got a chance to test, and see the bug, and #445 seems to fix, so now merged...
Yes, some They are still under test, as part of Tidy's international language support, but hopefully will be included in the next release... such an app would need access to the source, to even be able to use these API extension... they are presently only in Anyway, tests of version |
@marcograss, @AdamMajer, have you had a chance to test, re-test this? I just had a chance to built and run a sanitize Tidy version, in my RPI2/Raspbian/arm7 machine, using Can we close this? ... thanks... |
@marcograss just tried this Please feel free to re-open, or open another issue.... thanks... |
Hi,
I'm hitting this bug in the latest version 5.2.0 of tidy and also the master
unfortunately I'm not familiar with the project, so I didn't do any analysis, my env is ubuntu 16.04 fully updated
Marco
The text was updated successfully, but these errors were encountered: