Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: [Full-disclosure] noise about full-width encoding bypass? |
|---|---|
| Date: | Tue, 22 May 2007 16:33:54 +0400 |
Dear Brian Eaton, --Monday, May 21, 2007, 11:28:27 PM, you wrote to ascii@katamail.com: BE> Given how few application platforms decode full-width unicode to ASCII BE> equivalents, is there a case to be made that those application BE> platforms that do decide this conversion is a good idea are broken? BE> Put another way: should this be considered a bug in ASP.NET? BE> Regards, BE> Brian Converting e.g. Unicode full-width 'A' into ASCII 'A' is definitely valid and expected behavior. A bug is using unfiltered input in HTML/SQL generation. As for inability of content filter to catch this situation, it's just one more way to bypass it. See http://securityvulns.com/advisories/content.asp http://securityvulns.com/advisories/bypassing.asp -- ~/ZARAZA http://securityvulns.com/ Итак, я буду краток. (Твен) _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
| Previous by Date: | [Full-disclosure] KSign KSignSWAT ActiveX Control Multiple Buffer Overflows Vulnerability, BPS |
|---|---|
| Next by Date: | [Full-disclosure] Unicode Left/Right Pointing Double Angel Quotation Mark bypass?, 3APA3A |
| Previous by Thread: | Re: [Full-disclosure] noise about full-width encoding bypass?, Valdis . Kletnieks |
| Next by Thread: | Re: [Full-disclosure] [WEB SECURITY] Re: noise about full-width encoding bypass?, Chris Weber |
| Indexes: | [Date] [Thread] [Top] [All Lists] |