in reply to The danger of hidden fields

Well, from your description of the problem it seems to me that your attitude is correct. It bothers me that your boss should pay more attention to security.

I know very little about your actual scenario but I think there are a few main risks here (I assume that the script allows the customer data to be written to a file which is specified via a hidden field):

... Please do not take these as an extensive list. It's late and I only wrote what came to mind.

Now, so far you've acted ethically. No matter what people tells you do not try to expose or exploit this flaw without premission from your employer. If you succeed (and this seems easy from your description), this will allow your employer to sue you. You would not be the first to suffer through this nonsense. I say this because it is very tempting to exploit this vulnerability and play a little prank to your company as a proof of concept, but this can get you in serious trouble.

If after you ponint this to your boss, they still decide not to fix it, then leave it alone. And in a personal note, look for another job :)

Regards

Replies are listed 'Best First'.
Re: Re: The danger of hidden fields
by Anonymous Monk on Jul 23, 2002 at 10:45 UTC
    The heart may be in the wrong place, but trusting HTTP_REFERER for a validity check is not the right solution.

    Also if you are trusting user input to name a file, what if the user names a "file" (with proper encoding of course) something like | rm -rf /?