Re: [SMARTY] Serious security hole

From: Date: Sun, 02 Feb 2003 09:07:19 +0000
Subject: Re: [SMARTY] Serious security hole
References: 1  Groups: php.smarty.general 
Request: Send a blank email to php-smarty-general+get-7454@lists.php.net to get a copy of this message
On 1 Feb 2003 at 23:59, Monte Ohrt wrote: > Thanks for the heads up. The parser in the CVS version is much more > thorough, it only allows what is explicitly permitted, whereas in 2.3.1 > it is possible for things to slip through that are not explicitly > denied. I tried your example and it fails with errors, as it should. Let > me know if you see any problems with CVS. > > CVS also seems pretty stable, I don't know anything not working. The > next release is only waiting on documentation updates, I'll get that out > ASAP. > > Monte > That are great news! I didn't test the CVS version since I'm not very familiar with CVS and I didn't think the compiler was changed in CVS... But if the parser is stricter in the new release, the hole surely is closed. Nice that the bug is fixed before it was actually found out... :-) -- Ferdinand Beyer <fbeyer@clickhand.de>

« previous php.smarty.general (#7454) next »