> You mean to tell us that nmap is currently segfaulting for an industry
No, it is not segfaulting, and it is not exploitable.
Our libc contains a feature to detect backwards memcpy, in that case
it logs and KILLS THE PROCESS dead. There is no way to consider this
a risk.
The problem here is that nmap had a bug like this, in this decade.
The other problem is that dynamic checks, and static checks, didn't
find a problem which is so visible before it shipped.
No comments:
Post a Comment