close
One of the difficulties with spy tool applications is that even if they are legitimately used – the application vendor still has the problem of properly handling confidential data.
Case in point: Mobile-Spy for Windows Mobile.
Until recently (the last 48 hours or so) they had an issue with their web interface. The issue potentially allowed access to any communication data collected by their software.
Now that they've resolved the issue, we'll explain…
By using their Demo account to log onto their system, you were only supposed to be able to access demo messages. The logon is found at the following URL:
![Smart Demo](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/Smart_Demo.jpg&width=485&height=94)
This URL is from one of the demo messages that you're supposed to be able to view. Notice that the message ID is plainly visible in the URL. So, what happened if you changed the ID number in the URL?
![Demo URL](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/643_DemoURL.jpg&width=525&height=47)
We used 34841 as an example:
![Test URL](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/34841_URL.jpg&width=545&height=47)
Last week the result of adjusting the URL was this:
![Before](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/34841_Before.jpg&width=700&height=300)
And now the result is this:
![After](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/34841_After.jpg&width=700&height=300)
So, Mobile Spy has corrected the potential problem. You can read more details from ZDNet.
Case in point: Mobile-Spy for Windows Mobile.
Until recently (the last 48 hours or so) they had an issue with their web interface. The issue potentially allowed access to any communication data collected by their software.
Now that they've resolved the issue, we'll explain…
By using their Demo account to log onto their system, you were only supposed to be able to access demo messages. The logon is found at the following URL:
![Smart Demo](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/Smart_Demo.jpg&width=485&height=94)
This URL is from one of the demo messages that you're supposed to be able to view. Notice that the message ID is plainly visible in the URL. So, what happened if you changed the ID number in the URL?
![Demo URL](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/643_DemoURL.jpg&width=525&height=47)
We used 34841 as an example:
![Test URL](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/34841_URL.jpg&width=545&height=47)
Last week the result of adjusting the URL was this:
![Before](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/34841_Before.jpg&width=700&height=300)
And now the result is this:
![After](https://imageproxy.pixnet.cc/imgproxy?url=https://www.f-secure.com/weblog/archives/34841_After.jpg&width=700&height=300)
So, Mobile Spy has corrected the potential problem. You can read more details from ZDNet.
Posted by Jarno @ 12:22 GMT
http://www.f-secure.com/weblog/archives/00001285.html
全站熱搜