| Summary: | memory leak | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Xiaoyu He <1422930734> | ||||
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | bfulgham, darin, mcatanzaro, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
What would make a memory leak become an exploitable security issue? (In reply to Darin Adler from comment #2) > What would make a memory leak become an exploitable security issue? A remote attacker with operation privilege could exploit the vulnerability by sending specific messages continuously. Successful exploit may cause some service abnormal WebKit is filled with memory leaks. The worst that's going to happen is an OOM kill. We don't track these as security bugs. Your report from LeakSanitizer would be a lot more useful if you built with debuginfo enabled, so we can see what's going on. But the poc is sufficient for a bug report. |
Created attachment 423440 [details] poc ==3031==ERROR: LeakSanitizer: detected memory leaks Direct leak of 1088 byte(s) in 6 object(s) allocated from: #0 0x4e0ee0 (/root/targets/targets/jsc_afl_asan18+0x4e0ee0) #1 0x695e87e (/root/targets/targets/jsc_afl_asan18+0x695e87e) SUMMARY: AddressSanitizer: 1088 byte(s) leaked in 6 allocation(s).