-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IV support for first block decryption #3
Comments
Hi, thanks for the recommendation. Currently, the tool will take the first data chunk as IV automatically. In order to workaround your problem, you can append the IV to your data prior to sending the request to Padding Oracle Hunter. I agree for future improvement, the IV can be separated from the data to allow more flexibility. |
Ah, that doesn't sound like a safe assumption. The IV could be located anywhere, e.g. prepended or appended or somehow encoded with the ciphertext. Or sent in a completely separate parameter. Btw. I just had a very strange case, where the IV was hard-coded/static and always only one block of ciphertext present... which means padding oracle doesn't apply (but simply flipping a bit in the ciphertext should flip a bit in the cleartext). So some more information in the docs regarding IV and blocks would be good, too. |
Yeap, the limitation is known and for the next version, I will include an IV syntax with and IV field with different encoding option which allows user to place the IV anywhere in the request to accomodate more cases. Appreciate for coming up with the suggestion. |
It looks like the extension does not support an Initialization Vector as an input. It would be nice to have because if there is only one block of ciphertext available, we can still do the attack if the IV is sent to the server as well
The text was updated successfully, but these errors were encountered: