Didn't know about this one, ty!
Yeah, a lot of fuzzing is needed, I'll keep fuzzing some more tonight but yea I've tried setting headers too, urlencoding,unicode chars, etc
Do you know why we have this within your URL, its due to URLEncoding, I faced this same issue while fetching from an API, I got an error while I searched a query with spaces which breaks URL
Fix was to use the encodeURIcomponent method on the query parameter and it worked!
3/30
Solving SQLi, Path traversal and other vulnerabilities on portswigger is cool
but trying to exploit the same vulnerability on bwapp on level 2 difficulty is crazy as hell
Can anyone help me with bypassing this in a different way other than URLencoding?
Как проклят HTTP, часть №13
Сегодня я узнал, что существует 100500 различных вариантов URLEncoding и все они полусовместимы друг с другом
Мое любимое:
В Rust экосистеме есть percent-encoding, который, очевидно, кодирует спец символы как %byte ( )...
I'll go one step further: POST for every dynamic route!
• For params you can use request body JSON (instead of awkwardly urlencoding query params)
• No need to worry about caching intermediaries, it's often more trouble than it's worth
Totally agree. GET vs POST have meaningful behaviour differences in browsers. Use GET for stuff without side-effects, otherwise use POST.
The other verbs? Nah. I've always found it easier to be expressive in the URL than the HTTP verb.
friend came to me today asking if it was possible to fuzz with ffuf without urlencoding. url was /api/..\..\..\..\FUZZ - unfortunately we did not find a way to make ffuf not url encode this. solution was to use wfuzz which does not url encode. wfuzz.readthedocs.io/en/late…
Yes, still testing :)
To be fair, credit must go to @WickedCapsie who originally introduced the partial urlencoding technique in #DUSK. Urlencoding is a clever hack that saves lot of space. The standard and safest way is base64 encoding (originally introduced by @EgonFX ).
kepala dah mau pecah dan habis waktu seharian cuma karena salah pilih mode encoder: UrlEncoding vs StdEncoding -- demi cocok dengan output dari btoa()-nya JavaScript🤦♂️
pkg.go.dev/encoding/base64
suram.
Three days troubleshooting a service connector before I noticed someone had decided that URLEncoding the password value in the connection request was a good idea.
Heard some hackers in the space (mainly @hakluke) talking about espanso lately. Finally got the chance to sit down and install it and configure some stuff. Game changer. Also, if you all encode/decode base64 and urlencoding as much as I do, I'd recommend you make a hotkey for it.
New version of Hackvertor allows you to create custom tags in Java & Groovy. JavaScript is also supported on mac. Jwt tag is back. There is now the concept of local and global variable tags that can be shared across instances.Burp font size is now respected. Fixed urlencoding bug