full-disclosure - Re: SANS PHP Port Scanner Remote Code Execution

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAA24+d5m-AkBsXvPRUg11cxnPXbh39F0HjLOrNB6TB__X_z34w@mail.gmail.com>
Date: Wed, 6 Mar 2013 07:40:30 -0300
From: Ulisses Montenegro <ulisses.montenegro@...il.com>
To: Benji <me@...ji.com>
Cc: Full-Disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: SANS PHP Port Scanner Remote Code Execution

Not including proper input validation and error handling in code samples is
one of the most common and harmful practices in the software development
industry -- doing it is not "optional" or "advanced", it is mandatory
unless you want to be pwned.

Developers need to start doing things properly from the very beginning, as
habits become harder and harder to change with experience.


On Wed, Mar 6, 2013 at 7:33 AM, Benji <me@...ji.com> wrote:

> Actually, adding input sanitisation really wouldnt increase the code size
> that much. Are you just incompetent?
>
>
> On Wed, Mar 6, 2013 at 7:46 AM, Źmicier Januszkiewicz <gauri@....by>wrote:
>
>> Dear list,
>>
>> Well, I suppose this had to be a proof-of-concept piece of code to
>> demonstrate how port scanning can be done in PHP, not a production-grade
>> software. Adding input sanitization would increase the code size by a lot
>> and obscure the concept somewhat (not that there is much to be said anout
>> the concept though). Think we can give the dude some discount for that.
>>
>> Nevertheless, seeing something like this coming from "Certified Ethical
>> Hacker and Security + certified" makes me doubt the worthness of those
>> certificates. Could be nice to know the exact naming of those certificates
>> to properly disregard them in the future.
>>
>> With best regards,
>> Z.
>>
>> 2013/3/6 laurent gaffie <laurent.gaffie@...il.com>
>>
>>>
>>> http://resources.infosecinstitute.com/php-build-your-own-mini-port-scanner/
>>>
>>> Finding the vulnerability in this code is left as an exercise to the
>>> reader.
>>>
>>> PS: "*Your comment will be awaiting moderation forever."*
>>>
>>> _______________________________________________
>>> Full-Disclosure - We believe in it.
>>> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
>>> Hosted and sponsored by Secunia - http://secunia.com/
>>>
>>
>>
>>
>>
>> _______________________________________________
>> Full-Disclosure - We believe in it.
>> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
>> Hosted and sponsored by Secunia - http://secunia.com/
>>
>
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>



-- 
“If debugging is the process of removing software bugs, then programming
must be the process of putting them in.” - *Edsger Dijkstra*

Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/