Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Okay, Let's review:

All the customer data that is submitted to the script is as well as being emailed to us, stored in a text file. However the text file to store the data in is passed as a hidden field from the html, and there is no check to make sure that the referring page is the correct one.

So customer comes to the site, logs in, and currently their information (or more accurately, the location of the file containing the information) is passed via a hidden form field. There's no need for this really. The customer could just be passed a session identifier and all the remaining data would be stored on the server. This should be a relatively simple switch.

Now as for this:

cracker that saw his append and tracked him, or had been "casing the joint" for a couple of weeks, makes his move. Several (hundred) customers credit cards get used for whatever, and who gets the blame?

That's about equivalent to saying "if he puts locks on the doors and someone breaks in the next day, who's going to take the blame?" It's completely missing the point.

First off, there's no way a cracker's going to be monitoring a website with these vulnerabilities for weeks and not do anything. Secondly, not improving the security of a system for fear of being irrationally blamed for future incidents should be cause for dismissal on its own.


In reply to Re(4): The danger of hidden fields by cjf
in thread The danger of hidden fields by Gerard

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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 or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (3)
As of 2021-12-04 20:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    R or B?



    Results (30 votes). Check out past polls.

    Notices?