The Zebra issue is simply a default password/default configuration
issue. The documentation _clearly_ states that is should be changed and
than an 'enable password' be applied. In neither case does this allow
any "exploit" to take place, as you're restricted to the Zebra process
and not the OS.
It's no more of an exploit than Oracle's system/manager,
sys/change_on_install, or scott/tiger username/password combinations
that are installed by default.
Kind Regards,
-dsp
thanasonic (at) hack (dot) gr [email concealed] wrote:
> In-Reply-To: <005e01c48141$4e82f880$0701a8c0@COOKIE>
>
> Sorry for not mentioning that.Thats why the subject is called "SPECIAL FEATURE" and not a bug.
> By the way, the second issue about zebra its true and as i informed about it ,it can be exploited localy or remotely.
>
> Thanks for your reply,
> Thanasonic
>
>
issue. The documentation _clearly_ states that is should be changed and
than an 'enable password' be applied. In neither case does this allow
any "exploit" to take place, as you're restricted to the Zebra process
and not the OS.
It's no more of an exploit than Oracle's system/manager,
sys/change_on_install, or scott/tiger username/password combinations
that are installed by default.
Kind Regards,
-dsp
thanasonic (at) hack (dot) gr [email concealed] wrote:
> In-Reply-To: <005e01c48141$4e82f880$0701a8c0@COOKIE>
>
> Sorry for not mentioning that.Thats why the subject is called "SPECIAL FEATURE" and not a bug.
> By the way, the second issue about zebra its true and as i informed about it ,it can be exploited localy or remotely.
>
> Thanks for your reply,
> Thanasonic
>
>
[ reply ]