Extended Basic 7

[goluhaque]

i know d line where the bug is. is d function v hv 2 use is html_en**ty_de****() ?
if its a spoiler, sorry. im clueless.

[eljonto]

i know d line where the bug is. is d function v hv 2 use is html_en**ty_de****() ?

No

[Bv202]

This ******.

I know exactly what the bug and vuln is. I also know how to fix it, but it just doesn't accept my answer.

Can't I just PM someone with my answer so you could give me a hint what's wrong? I can't post what I'm doing without spoiling everything.

[nermd]

you can send me a pm ...

[Bv202]

I'll do, thanks

[tremor77]

I saw the problems in the code as soon as I opened the page...

that being said, took a little over 3 hours to get the 'right' fix as you have it.... should consider editing the mission answer check for the other possible answers that IMHO are also very much correct...

sorry if this has been said a billion times but I just needed to vent that.

[trandoanhung1991]

Ok, so I changed the method, and used htmls***********_d*c*** with ENT_QUOTES. What else do I need? Sorry if I sound rude but this one's getting on my nerves

[st0w]

Ok, so I changed the method, and used htmls***********_d*c*** with ENT_QUOTES. What else do I need? Sorry if I sound rude but this one's getting on my nerves

That's not the right function to use. Think about what the function you're talking about would do. Think about what type of attack you're trying to prevent. Are the answers to those questions the same, or are they mutually exclusive?

As has already been said multiple times - there are several perfectly valid ways to prevent exploitation of the presented vuln. And the code should really allow any of the various alternatives... But currently, it does not. Which can be helpful on the one hand, because it forces you to think about all the different ways you can accomplish the task. Unless, of course, your first guess is the right one.

[kaoS555]

OMG this one took me forever to figure out, but I just got it after visiting a few of the links provided in this thread. It is all in how you sanitize to prevent the XSS vuln, I feel so special now.

[Mr Fredward]

I cheated and looked up the answer after 2 hours of trying to guess what kind of sanitization the knuckle head who wrote this challenge liked best. Since the challenge is about identifying the vulnerability, not wasting your life guessing sanitization, I don't think its a spoiler to say don't waste time with php sanitization functions like I did, and instead look at string functions meant to encode special chars, particularly chars that are special in html. *wink wink nudge nudge*

http://www.php.net/manual/en/ref.strings.php

All you need to do is sanitize and fix a simple bug, don't overthink it and change the way it gets the dangerous string entirely.