Professional Documents
Culture Documents
BY
Can virus infect the mobile phones? It is a million dollar question that has
no answer up to now. The chance is increasing day by day and recent hoax virus, Spam
SMS worms is an evidence of it. Due to the financial aspects associated with wireless
communications, this subject is under through research now.
The WAP protocol is now the leading standard for information services
on wireless terminals like digital mobile phones. By the use of WAP, there is a
possibility of wireless devices like mobile phones, getting infected with virus and
worms. Though up to now there is no such attack, as the usage of script languages
increases, there is a chance of malicious code injection.
Wireless application protocol is an application environment and a set of
communication protocols for wireless devices. It enables the wireless devices,
independent access to the Internet. WAP bridges the mobile world and the Internet. It
also connects the corporate intranets. Due to this users can access the same amount of
information by using a packet-sized device as they can from a desktop PC.
This section does not discuss the technical solutions of how to detect such threats.
Products with the ability to detect current JavaScript or Visual Basic Script threats should
require little if any modification to detect future WML and WMLScript threats. This
section only discusses the advantages and disadvantages of solution placement.
7.1 On-Device Solution
Placing a scanner on the device can be effective in blocking content, but may be
resource intensive and difficult in regards to development. WAP devices vary from
phones to personal digital assistants (PDAs) and each of the devices may be running on
non-updatable and proprietary operating systems. One could not create a single solution
that could be placed on all devices. In addition, updating the firmware or software may be
problematic.
While possible, on-device solutions do not seem practically viable.
7.2 Origin Server Solution
Origin servers are generally run on popular operating systems such as Unix or
NT. Existing products can scan these servers. The existing products would need to be
updated with new signature files to detect malicious WML (Script) code, but this would
be trivial for any scanner that can currently handle JavaScript or Visual Basic Script
threats.
However, limiting the solution to the origin server does not adequately protect the
end user. While the origin server administrator could assure his systems are free from
malicious content, the end user could not be assured any origin server visited is free from
malicious content.
Most anti-virus products currently have the technology to detect WML or WMLScript
threats. These engines would simply need to be wrapped to interact with the WAP
gateway components.
8. Summary
While currently, WML (Script) does not pose a great threat for malicious content
today, it may in the future. Before such threats are possible, the WML (Script)
specifications must provide more robust functionality.Once the functionality is possible,
WML (Script) malware still may not be a large threat. Other environmental factors from
market penetration to social engineering play a role in the ability of threats to spread. The
role of these factors is outside the scope of this document.
In general, security vendors should already have the technology to detect such threats.
Security product engines need to be wrapped to interact with the appropriate components
or run on the appropriate operating systems.
Finally, users should extend their safe computing practices to such devices and avoid
questionable executable content.
9. References
1. WAP Architecture, Version 30-Apr-1998, Wireless Application Protocol Forum,
Ltd.
2. WAP Service Indication, Version 08-Nov-1999, Wireless Application Protocol
Forum, Ltd.
3. WAP Push Architectural Overview, Version 08-Nov-1999, Wireless Application
Protocol Forum, Ltd.
4. WAP PPG Service, Version 16-August-1999, Wireless Application Protocol
Forum, Ltd.
5. WAP Push Access Protocol, Version 08-Nov-1999, Wireless Application
Protocol Forum, Ltd.
WML Reference, Version 1.1, Nokia
6. WMLScript Reference, Version 1.1, Nokia