This article has been archived. It is offered "as is" and will no longer be updated.
Embedded null characters in some postions in a URL may not be detected as tags and may bypass the request script validation functionality.
This problem occurs because during parsing, the ASPNET scripting tag detection mechanism looks for an angle bracket ("<") that is followed by a letter or by an exclamation point ("!"). When the tag detection mechanism finds a null character instead, the script does not see the angle bracket ("<") as a tag.
The request will render script or active content. The expected result is a request validation error or inert content.
How to Obtain the Hotfix
This issue is fixed in the June 2003 ASP.NET Hotfix Package 1.1. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
821156 INFO: ASP.NET 1.1 June 2003 Hotfix Rollup Package
You cannot obtain this fix individually. You must install the rollup.
Note When you request this hotfix, you receive the rollup. The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.