Closed Hlynrkjaer closed 6 years ago
Hi,
Sorry for the delayed answer. The developer console means your browsers developer tools. See for example: https://developer.chrome.com/devtools
I just tried following the example and it worked fine for me.
Hello,
So, I got the proper view! SORRY for confusion. Steps, of course, are valid and worked. Even I completed this task before (and it was a reason for this ask - because eventually current experience was with broken result).
I confused with tries to change 'value' as string than proper change 'value' as 'value' of option ( :-/ ). Not sure why I did not re-check it more properly before this ask. Maybe because confused by WebGoat's suggested solution/tips.
Sorry else one time.
Thanks for your response, @nygrenh !
Hello,
Part Three of Securing Software course with next example of reporting vulnerability (steps to reproduce trouble):
But (?!) looks like that it should not work with WebGoat (?!). At least, such steps should not be enough. Or should be based on certain advanced 'developer console' (?!). Does it possible to verify that provided example steps indeed valid for reproducing this trouble-example under WebGoat? I tried only with Windows 10 (different browsers) - where it's not valid steps (or...).
Own WebGoat's hints about using WebScarab (as potential hook for request to server and modify it on-the-fly?!).
Thanks!