Security slicing for auditing common injection vulnerabilities

Cross-site scripting and injection vulnerabilities are among the most common and serious security issues for Web applications. Although existing static analysis approaches can detect potential vulnerabilities in source code, they generate many false warnings and source-sink traces with irrelevant in...

Full description

Saved in:
Bibliographic Details
Main Authors: THOME, Julian, SHAR, Lwin Khin, BIANCULLI, Domenico, BRIAND, Lionel
Format: text
Language:English
Published: Institutional Knowledge at Singapore Management University 2017
Subjects:
Online Access:https://ink.library.smu.edu.sg/sis_research/4894
https://ink.library.smu.edu.sg/context/sis_research/article/5897/viewcontent/Security_slicing___PV.pdf
Tags: Add Tag
No Tags, Be the first to tag this record!
Institution: Singapore Management University
Language: English
id sg-smu-ink.sis_research-5897
record_format dspace
spelling sg-smu-ink.sis_research-58972020-02-13T08:17:58Z Security slicing for auditing common injection vulnerabilities THOME, Julian SHAR, Lwin Khin BIANCULLI, Domenico BRIAND, Lionel Cross-site scripting and injection vulnerabilities are among the most common and serious security issues for Web applications. Although existing static analysis approaches can detect potential vulnerabilities in source code, they generate many false warnings and source-sink traces with irrelevant information, making their adoption impractical for security auditing. One suitable approach to support security auditing is to compute a program slice for each sink, which contains all the information required for security auditing. However, such slices are likely to contain a large amount of information that is irrelevant to security, thus raising scalability issues for security audits. In this paper, we propose an approach to assist security auditors by defining and experimenting with pruning techniques to reduce original program slices to what we refer to as security slices, which contain sound and precise information. To evaluate the proposed approach, we compared our security slices to the slices generated by a stateof-the-art program slicing tool, based on a number of open-source benchmarks. On average, our security slices are 76 % smaller than the original slices. More importantly, with security slicing, one needs to audit approximately 1% 2017-02-01T08:00:00Z text application/pdf https://ink.library.smu.edu.sg/sis_research/4894 info:doi/10.1016/j.jss.2017.02.040 https://ink.library.smu.edu.sg/context/sis_research/article/5897/viewcontent/Security_slicing___PV.pdf http://creativecommons.org/licenses/by-nc-nd/4.0/ Research Collection School Of Computing and Information Systems eng Institutional Knowledge at Singapore Management University Security auditing static analysis vulnerability automated code fixing Information Security
institution Singapore Management University
building SMU Libraries
continent Asia
country Singapore
Singapore
content_provider SMU Libraries
collection InK@SMU
language English
topic Security auditing
static analysis
vulnerability
automated code fixing
Information Security
spellingShingle Security auditing
static analysis
vulnerability
automated code fixing
Information Security
THOME, Julian
SHAR, Lwin Khin
BIANCULLI, Domenico
BRIAND, Lionel
Security slicing for auditing common injection vulnerabilities
description Cross-site scripting and injection vulnerabilities are among the most common and serious security issues for Web applications. Although existing static analysis approaches can detect potential vulnerabilities in source code, they generate many false warnings and source-sink traces with irrelevant information, making their adoption impractical for security auditing. One suitable approach to support security auditing is to compute a program slice for each sink, which contains all the information required for security auditing. However, such slices are likely to contain a large amount of information that is irrelevant to security, thus raising scalability issues for security audits. In this paper, we propose an approach to assist security auditors by defining and experimenting with pruning techniques to reduce original program slices to what we refer to as security slices, which contain sound and precise information. To evaluate the proposed approach, we compared our security slices to the slices generated by a stateof-the-art program slicing tool, based on a number of open-source benchmarks. On average, our security slices are 76 % smaller than the original slices. More importantly, with security slicing, one needs to audit approximately 1%
format text
author THOME, Julian
SHAR, Lwin Khin
BIANCULLI, Domenico
BRIAND, Lionel
author_facet THOME, Julian
SHAR, Lwin Khin
BIANCULLI, Domenico
BRIAND, Lionel
author_sort THOME, Julian
title Security slicing for auditing common injection vulnerabilities
title_short Security slicing for auditing common injection vulnerabilities
title_full Security slicing for auditing common injection vulnerabilities
title_fullStr Security slicing for auditing common injection vulnerabilities
title_full_unstemmed Security slicing for auditing common injection vulnerabilities
title_sort security slicing for auditing common injection vulnerabilities
publisher Institutional Knowledge at Singapore Management University
publishDate 2017
url https://ink.library.smu.edu.sg/sis_research/4894
https://ink.library.smu.edu.sg/context/sis_research/article/5897/viewcontent/Security_slicing___PV.pdf
_version_ 1770575088523935744