# UTF-8 Locator ‌You can make use of the UTF locator to discover bugs on applications that accept user-supplied input. \ In UTF-8, characters are encoded using sequences of 1 to 6 octets. The only octet of a "sequence" of one has the higher-order bit set to 0, the remaining 7 bits being used to encode the character value. In a sequence of n octets, n1, the initial octet has the n higher-order bits set to 1, followed by a bit set to 0. The remaining bit(s) of that octet contain bits from the value of the character to be encoded. \ The following octet(s) all have the higher-order bit set to 1 and the following bit set to 0, leaving 6 bits in each to contain bits from the character to be encoded. ‌ In a nutshell, this UTF locator could be used to trigger encoding/decoding issues among applications that could later on, after or pre-process, trigger different types of behaviours, and it depends on the application and platform how this is handled. ‌ Fill in "message to include'' ( this is optional ) and use the default amount "10.000" or change it for more or less as needed. Click on "**Create UTF**'' to run it. This action will create a file called utflocator.txt and will also show the content of the file. Copy the file to its destination or copy the content and add it to a user-supplied input to trigger, or try to, a vulnerability. ![](https://1112023788-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MU9W-baGw5TeUzNXoyo%2F-MdR_K5jGL1BbZ03DySo%2F-MdRbC1a5Lo7wTU6Gf66%2F21.png?alt=media\&token=b350d3e9-1a95-4c19-971a-02fc62e32cf7) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://exploit-pack.gitbook.io/exploit-pack-manual-pages/master/utf-8-locator.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.