25-03-2017, 09:37 AM
It's a million dollar question that has no answer so far. The result is increasing day to day scam virus, spam sms worms. Due to the financial aspects associated with wireless communications, this topic is under investigation through now. The WAP protocol is the leading standard in information services on wireless terminals such as digital mobile phones. Using, there is a possibility that wireless devices will become infected with viruses and worms. Although so far fewer attacks of this type, as the use of scripting languages increases, there is a possibility of malicious code injection. The wireless application protocol is an application environment and a set of communication protocols for wireless devices. Allows wireless devices to access the Internet independently. WAP bridges the mobile world and the Internet. It also connects corporate intranets. Because of this, users can access the same amount of information using a packet size device as they can from a desktop PC.
The WAP standard is based on Internet standards (HTML, XML and TCP / IP). It consists of a WML language, a WML script and a wireless telephony application interface (WTAI). The use of mobile phones with WAP is booming. WAP-enabled cell phones allow users to access a wide variety of services. WAP enables users to do online banking, monitor stock markets, use email and access the Internet - all from their mobile phones. The new services are developed every day and as the scripts become more robust, the possibility that the malicious code increases.
This document will discuss the threats with the current WAP protocol and how the changes in the protocol and the increase in its use will allow the entry of real viruses. Future threat scenarios are presented along with suggestions to avoid these problems. This document also presents an overview of WAP, WAP Push, WML and WMLScript and its ability to host malicious software. Finally, to detect future threats, the possible location of the solution will be presented.
The growth of Internet media is motivated by high-speed bandwidth. Concern over small simplified content is diminishing with the advent of cheap 24x7 high speed connections for home and business. However, computing devices are becoming smaller and more portable with a relatively smaller bandwidth for Internet content - hence the desire for a smaller media format. WAP specifically addresses these needs with WML and WMLScript, designed for small screen sizes, limited input devices, low-resource devices, and narrowband connectivity.
WAP model
The WAP programming model is similar to the current HTTP model. WAP consists of a client, a gateway and a source server.
1. The user makes a request for content.
2. The WAE (Wireless Application Environment) user agent encodes the request.
3. The WAE user agent sends the request to the gateway.
4. The Gateway decodes the request.
5. The gateway translates the request (to HTTP) and sends it to the source server.
6. The source server returns the appropriate content.
7. If necessary, the gateway translates the content (HTML to WML).
8. The gateway encodes the content.
9. The Gateway sends the encoded content to the Client
10. The WAE user agent interprets the encoded content and presents it to the user.
The WAP standard is based on Internet standards (HTML, XML and TCP / IP). It consists of a WML language, a WML script and a wireless telephony application interface (WTAI). The use of mobile phones with WAP is booming. WAP-enabled cell phones allow users to access a wide variety of services. WAP enables users to do online banking, monitor stock markets, use email and access the Internet - all from their mobile phones. The new services are developed every day and as the scripts become more robust, the possibility that the malicious code increases.
This document will discuss the threats with the current WAP protocol and how the changes in the protocol and the increase in its use will allow the entry of real viruses. Future threat scenarios are presented along with suggestions to avoid these problems. This document also presents an overview of WAP, WAP Push, WML and WMLScript and its ability to host malicious software. Finally, to detect future threats, the possible location of the solution will be presented.
The growth of Internet media is motivated by high-speed bandwidth. Concern over small simplified content is diminishing with the advent of cheap 24x7 high speed connections for home and business. However, computing devices are becoming smaller and more portable with a relatively smaller bandwidth for Internet content - hence the desire for a smaller media format. WAP specifically addresses these needs with WML and WMLScript, designed for small screen sizes, limited input devices, low-resource devices, and narrowband connectivity.
WAP model
The WAP programming model is similar to the current HTTP model. WAP consists of a client, a gateway and a source server.
1. The user makes a request for content.
2. The WAE (Wireless Application Environment) user agent encodes the request.
3. The WAE user agent sends the request to the gateway.
4. The Gateway decodes the request.
5. The gateway translates the request (to HTTP) and sends it to the source server.
6. The source server returns the appropriate content.
7. If necessary, the gateway translates the content (HTML to WML).
8. The gateway encodes the content.
9. The Gateway sends the encoded content to the Client
10. The WAE user agent interprets the encoded content and presents it to the user.