Vladimir '3APA3A' Dubrovin
11/12/08, 18:25
Dear s.gottschall@dd-wrt.com,
According to current practices, it's considered as a security
vulnerability. The fact you must be logged in to device in browser is a
mitigation factor.
To protect routers against attacks like this either generate some kind
of non-predictable session id as a hidden field in any HTML form and
check this id or check Referer:.
--Wednesday, December 10, 2008, 3:22:56 PM, you wrote to bugtraq@securityfocus.com:
sgdwc> this is no security flaw since you must be already logged in
within the webinterface of dd-wrt. otherwise this here will not work. we
already fixed this issue in our sourcetree
--
~/ZARAZA http://securityvulns.com/
Ïàòðèîòèçì - ýòî òà æå ðåëèãèÿ. (Òâåí)
According to current practices, it's considered as a security
vulnerability. The fact you must be logged in to device in browser is a
mitigation factor.
To protect routers against attacks like this either generate some kind
of non-predictable session id as a hidden field in any HTML form and
check this id or check Referer:.
--Wednesday, December 10, 2008, 3:22:56 PM, you wrote to bugtraq@securityfocus.com:
sgdwc> this is no security flaw since you must be already logged in
within the webinterface of dd-wrt. otherwise this here will not work. we
already fixed this issue in our sourcetree
--
~/ZARAZA http://securityvulns.com/
Ïàòðèîòèçì - ýòî òà æå ðåëèãèÿ. (Òâåí)