It's not too hard to test for command injection, SQL injection or cross site scripting "potential". As to actually being able to exploit the vulnerability, that probably depends on the penetration tester experience. You're better safe than sorry, don't depend on "security through obscurity" and cross your "t"s, dot your "i"s.
- use taint mode
- sanitize your external inputs and accept only what you expect to get (numbers, strings, specific sizes, etc)
- use placeholders for SQL values
- use system(), exec() in list context
- have your design and code reviewed by a peer
- implement good audit logs and backups (update)
Tiago
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
