GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - JoshuaProvoste/URL-Encode-Injection: Curated UTF-8 URL-encoded character dictionary for injection testing, fuzzing, and bypass techniques against web applications and APIs, focused on null byte injection, double encoding, and input validation evasion scenarios.

BranchesTags
Open more actions menu

Latest commit

 

History

8 Commits
8 Commits

Folders and files

NameName
Last commit message
Last commit date
README.md
README.md
 
 
url_encode_utf_8_basic.txt
url_encode_utf_8_basic.txt
 
 

Repository files navigation

URL Encode Injection (UTF-8)

Basic list of URL encoded UTF-8 characters for injection attacks. These types of attacks allows get bypass of login screens, database dumps, generation of custom payloads URL encode based, and many others results.

  • %00
  • %01
  • %02
  • %03 ...

Scope

With this basic list is possible make injections of special characters on web apps, API endpoints, and many other technologies. The purpose of these injections is to intentionally cause errors to obtain unexpected behaviors.

References

Nowadays, there are no public references because is my own idea to bring Null Byte Injection to the category of brute force or fuzzing process.

However, you can read more about Null Byte Injection and URL encoded attacks:

  • https://owasp.org/www-community/Double_Encoding
  • https://en.wikipedia.org/wiki/Null_character
  • https://www.cgisecurity.com/lib/URLEmbeddedAttacks.html
  • https://owasp.org/www-community/attacks/Embedding_Null_Code
  • https://book.hacktricks.xyz/pentesting-web/file-inclusion#basic-lfi-and-bypasses

Example

If you have an API endpoint like this /v1/product/some-id/price or whatever similar, you can send the endpoint to Burp Suite Intruder and pass your URL encode dictionary in order to replace §some-id§, and inspect the responses.

§some-id§ can be a uuid, hash or whatever are used insted of "id".

Like Null Byte Injection, the URL Encode Injection can be passed at the beginning or the end of your target entry point:

  • /v1/product/§dictionary§/price
  • /v1/product/some-id§dictionary§/price
  • /v1/product/§dictionary§some-id/price

Custom & Advanced Dictionaries

If you want make your own dictionary and delve into the subject, i recommend the following character collection:

  • https://www.fileformat.info/info/charset/index.htm

About

Curated UTF-8 URL-encoded character dictionary for injection testing, fuzzing, and bypass techniques against web applications and APIs, focused on null byte injection, double encoding, and input validation evasion scenarios.

Topics

fuzzinginjectioninjection-attacksinput-validationnull-bytepentestingurl-encodeurl-encodingweb-security

Resources

Readme
Activity

Stars

13 stars

Watchers

1 watching

Forks

2 forks
Report repository

Releases

Packages

Contributors

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.