Efficient array & pointer bound checking against buffer overflow attacks via hardware/software

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

3 Scopus citations

Abstract

Buffer overflow attacks cause serious security problems. Array & pointer bound checking is one of the most effective approaches for defending against buffer overflow attacks when source code is available. However, original array & pointer bound checking causes too much overhead since it is designed to catch memory errors and it puts too many checks. In this paper, we propose an efficient array & pointer bound checking strategy to defend against buffer overflow attacks. In our strategy, only the bounds of write operations are checked. We discuss the optimization strategy via hardware/software and conduct experiments. The experimental results show that our strategy can greatly reduce the overhead of array & pointer bound checking. Our conclusion is that based on our strategy, array & pointer bound checking can be a practical solution for defending systems against buffer overflow attacks with tolerable overhead.

Original languageEnglish
Title of host publicationProceedings ITCC 2005 - International Conference on Information Technology
Subtitle of host publicationCoding and Computing
EditorsH. Selvaraj, P.K. Srimani
Pages780-785
Number of pages6
StatePublished - 2005
Externally publishedYes
EventITCC 2005 - International Conference on Information Technology: Coding and Computing - Las Vegas, NV, United States
Duration: 4 Apr 20056 Apr 2005

Publication series

NameInternational Conference on Information Technology: Coding and Computing, ITCC
Volume1

Conference

ConferenceITCC 2005 - International Conference on Information Technology: Coding and Computing
Country/TerritoryUnited States
CityLas Vegas, NV
Period4/04/056/04/05

Fingerprint

Dive into the research topics of 'Efficient array & pointer bound checking against buffer overflow attacks via hardware/software'. Together they form a unique fingerprint.

Cite this