ValueGuard: protection of native applications against data-only buffer overflows

  • Authors:
  • Steven Van Acker;Nick Nikiforakis;Pieter Philippaerts;Yves Younan;Frank Piessens

  • Affiliations:
  • IBBT-Distrinet, Katholieke Universiteit Leuven, Leuven, Belgium;IBBT-Distrinet, Katholieke Universiteit Leuven, Leuven, Belgium;IBBT-Distrinet, Katholieke Universiteit Leuven, Leuven, Belgium;IBBT-Distrinet, Katholieke Universiteit Leuven, Leuven, Belgium;IBBT-Distrinet, Katholieke Universiteit Leuven, Leuven, Belgium

  • Venue:
  • ICISS'10 Proceedings of the 6th international conference on Information systems security
  • Year:
  • 2010

Quantified Score

Hi-index 0.00

Visualization

Abstract

Code injection attacks that target the control-data of an application have been prevalent amongst exploit writers for over 20 years. Today however, these attacks are getting increasingly harder for attackers to successfully exploit due to numerous countermeasures that are deployed by modern operating systems. We believe that this fact will drive exploit writers away from classic control-data attacks and towards data-only attacks. In data-only attacks, the attacker changes key data structures that are used by the program's logic and thus forces the control flow into existing parts of the program that would be otherwise unreachable, e.g. overflowing into a boolean variable that states whether the current user is an administrator or not and setting it to "true" thereby gaining access to the administrative functions of the program. In this paper we present ValueGuard, a canary-based defense mechanism to protect applications against data-only buffer overflow attacks. ValueGuard inserts canary values in front of all variables and verifies their integrity whenever these variables are used. In this way, if a buffer overflow has occurred that changed the contents of a variable, Value-Guard will detect it since the variable's canary will have also been changed. The countermeasure itself can be used either as a testing tool for applications before their final deployment or it can be applied selectively to legacy or high-risk parts of programs that we want to protect at run-time, without incurring extra time-penalties to the rest of the applications.