Home page logo

fulldisclosure logo Full Disclosure mailing list archives

Re: JavaScript exploits via source code disclosure
From: Valdis.Kletnieks () vt edu
Date: Thu, 06 May 2010 08:56:23 -0400

On Thu, 06 May 2010 01:03:09 PDT, Ed Carp said:
Just for clarification, the business wants to put client-side
Javascript on a customer-facing web site, and it's my job to figure
out how to protect the back-end web services...sigh...

Get a copy of Firefox.  Install the Tamper Data extension:

Play a bit. Learn the two biggest secrets of Javascript web security:

1) In the end, you can't use Javascript to keep a determined attacker from
figuring out what you're sending to the web site.

2) You also can't depend on Javascript to prevent the attacker from sending
other (potentially tampered) requests.

These are basically special cases of a more general principle:  You can't
depend on enforcing security using code that's running under the control
of the attacker. Unfortunately, a lot of people in this industry don't
understand this...

Your best strategy for securing the back end is to simply forget about the
Javascript, and just assume from the start that your attacker *can* and *will*
send you malicious crafted requests (xss, sql injection, forged session
cookies, or whatever). In general - if it makes you say "Oh, receiving *that*
would suck", it will be sent. And the more suckage it would cause, the
more you should expect the tampered request.

Attachment: _bin

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

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]