15.11.2012 Views

icegov2012 proceedings

icegov2012 proceedings

icegov2012 proceedings

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

is with a view to using websites which files has been highly<br />

populated in the search engine database.<br />

3.1 Testing tool<br />

The second phase was to choose a software testing tool to scan for<br />

web vulnerabilities. Several criteria were part of the decision in<br />

choosing the testing tool. First, the testing software must be<br />

compatible with the windows operating system since the test was<br />

carried out on the researchers’ personal computer systems (PC).<br />

Secondly, the software must have specific vulnerability testing<br />

options to scan web sites, as opposed to common server-based<br />

scanning products. After review of different web scanners,<br />

Acunetix Web Vulnerability Scanner was employed. This is noted<br />

to be in the same category with Nmap, which has been widely<br />

used [1]. Acunetix was used to test different web application<br />

vulnerability issues including: Cross-Site Script (XSS), SQL<br />

injection (SQLi), cookie manipulation (CM), unencrypted<br />

password (UP) and broken links (BL) of the web pages, which are<br />

main targets here. The choice of these parameters is premised on<br />

the high impact of its severity compared to others. In addition to<br />

this testing tool, manual testing was also carried out on some few<br />

websites in a way as not to leave footprints on the website. This is<br />

necessary in order to confirm the results generated by Acunetix<br />

web vulnerability scanners.<br />

3.2 Procedure<br />

After launching the web scanner, the desired Universal Resource<br />

Location (URL) is entered in the wizard box provided and the<br />

‘go’ button is fired. If the Internet connection on the computer is<br />

available then the scanner will begin the process. The scanner<br />

(Acunetix), thus virtually crawl the website of any given URL and<br />

presents the analysis of the vulnerability for every run. The<br />

Internet connection used for the exercise is a 3.5G on a High<br />

Speed Downlink Packet Access (HSPDA). The scanning process<br />

took on average 25 minutes, although the times varied from 15<br />

minutes up to 1 hour depending on the size of the entire given<br />

website. The manual test for XSS as well as SQLi was carried out<br />

to confirm the results generated by the vulnerability scanner. This<br />

is possible when such scripts as alert (‘This website is<br />

vulnerable’) is inputted into any available input field<br />

such as: the search, feedback and form fields within the website<br />

and the action button is pressed thereafter. If the web page is<br />

vulnerable, a Java script enabled browser will show a java script<br />

pop-up alert window containing the text in the parenthesis, ‘This<br />

website is vulnerable’. Also to manually test for SQL injection<br />

vulnerabilities, a single quote ( ' ) can be used as input. The single<br />

quote is a special character in SQL, and if it is included in the<br />

SQL query it will most likely generate an SQL statement error.<br />

All the 64 Nigerian government websites were tested over a<br />

period of two weeks within the month of August 2011 and<br />

technical report was produced for each site, listing the types and<br />

numbers of specific vulnerabilities. Each report was divided into<br />

several sections listing four levels of security vulnerability: High,<br />

Medium, Low and Informational. High level – these are critical<br />

problems which could cause high risk damage to the website e.g<br />

website defacement [1], database manipulation and modification<br />

[6], phishing, identity theft [1] amongst others. Medium and Low<br />

level – these are problems that could pose some level of risk to<br />

users of the web application. Informational – these are messages<br />

that probably have little risk to users, but still should be analyzed<br />

238<br />

by web developers because of the possibility of creating high<br />

vulnerabilities. The sites tested were categorized into Agencies,<br />

Judiciary, Law Enforcement/Defence, Media, Ministries,<br />

Parastatals, States and Others categories.<br />

4.0 RESULTS AND DISCUSSION<br />

Out of the 64 Nigerian government sites tested, 27, which<br />

represent 42.2% were vulnerable to XSS while 31.3% are<br />

vulnerable to SQLi. It was also discovered that 37.5% and 70.3%<br />

were vulnerable to unencrypted password and broken links<br />

respectively. These findings are represented and summarized<br />

mathematically in algebraic expressions using set theory as shown<br />

in Table 1.<br />

Table 1: Algebraic representation of e-government vulnerabilities<br />

in Nigeria<br />

Algebraic<br />

Expressions<br />

Interpretations<br />

U = 64 the universal set, i.e total sample tested.<br />

n(XSS) = 27 the number of websites vulnerable to<br />

XSS.<br />

n(SQLi) = 20 the number of websites vulnerable to<br />

SQL injection<br />

n(UP) = 24 the number of websites vulnerable to UP<br />

n(BL) = 45 the number of websites vulnerable to BL<br />

n(SQLi ∪ XSS) =<br />

34<br />

n(SQLi ∩ XSS) =<br />

13<br />

n(SQLi ∩ XSS 1 ) =<br />

7<br />

n(SQLi 1 ∩ XSS) =<br />

14<br />

n(U - (SQLi ∪<br />

XSS) 1 ) = 30<br />

the number of websites vulnerable to<br />

both SQL injection & XSS<br />

the number of websites exclusively<br />

vulnerable to both SQL injection & XSS<br />

the number of websites vulnerable to<br />

SQL injection but not XSS<br />

the number of websites vulnerable to<br />

XSS but not SQL injection<br />

the number of websites vulnerable to<br />

other parameters under test but not XSS<br />

nor SQL injection<br />

Legend: SQLi – Structured Query Language injection<br />

XSS – Cross Site Scripting<br />

UP – Unencrypted Password<br />

BL – Broken Links<br />

Table 2 shows the distribution of vulnerability in each category,<br />

for example apart from other categories which constitute the<br />

highest percentage of XSS vulnerability; the judiciary followed by<br />

one out of every four being vulnerable 25% relative to the<br />

participation in the test.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!