https://sourceware.org/bugzilla/show_bug.cgi?id=33548
--- Comment #1 from Nick Alcock <nick.alcock at oracle dot com> --- See libctf/33549: malformed input is not really in libctf's threat model (not historically and I haven't gone to extreme lengths to avoid it even now, though I'm adding more range checking all the time). If your CTF has a valid magic number, it should be valid CTF: there are many, many places where feeding custom garbage in instead can cause trouble. (But this specific case you highlight here will be fixed by CTFv4.) This sensitivity to garbage will be somewhat reduced in v4, but almost certainly not fixed entirely, at least not in one go. -- You are receiving this mail because: You are on the CC list for the bug.
