Cenzic 232 Patent
Paid Advertising
sla.ckers.org is
ha.ckers sla.cking
Sla.ckers.org
Where you should disclose your vulnerabilities. Go read RFPolicy if you want to do responsible disclosure, and go here for when all else fails. 

Current Page: 1 of 1
Results 1 - 4 of 4
4 years ago
landijk
YUI is a Javascript widget library developed by Yahoo!. Their table widget, called DataTable, by default renders data as HTML fragments. The default formatter for rendering table cells is below: ____formatDefault : function(el, oRecord, oColumn, oData) { ______el.innerHTML = oData === undefined || __________oData === null || __________(typeof oData === 'number' && isNaN(oData)) ?
Forum: Full Disclosure
6 years ago
landijk
"I don't think I can come up with a case where the HtmlEncode method will leave us with an exploitable condition." I can't think of one either, but for me, the issue is broader than just exploitability. An encoding method should have certain formal properties, and in this case one of these properties is that, given an arbitrary String s (in the .NET sense), the below XML snippet when
Forum: XSS Info
6 years ago
landijk
"...they automatically go through the correct encoding methods." That sounds right to me. However, the user-accessible System.Web.HTTPUtility.HTMLEncode and HTMLAttributeEncode methods don't work very well. They both fail on low-ASCII control characters, null bytes in particular, and it looks like their attribute encoder encodes just 3 characters! You are better off writing your ow
Forum: XSS Info
6 years ago
landijk
The current version of the framework (.NET 3.5) removes null bytes, then looks for the below pairs of characters. Neither the examples in this thread nor any of the vectors on the XSS cheat sheet will get past the validator. Assuming you have access to Windows, you can test the validator yourself by downloading MS Visual Web Developer 2008 Express Edition, which is free (for "hobbyist use&q
Forum: XSS Info
Current Page: 1 of 1