Is Your Software on Dope? - Formal Analysis of Surreptitiously "enhanced" Programs

Pedro R. D'Argenio, Gilles Barthe, Sebastian Biewer, Bernd Finkbeiner, Holger Hermanns

Abstract

Usually, it is the software manufacturer who employs verification or testing to ensure that the software embedded in a device meets its main objectives. However, these days we are confronted with the situation that economical or technological reasons might make a manufacturer become interested in the software slightly deviating from its main objective for dubious reasons. Examples include lock-in strategies and the \(\mathrm {NO}_x\) emission scandals in automotive industry. This phenomenon is what we call software doping. It is turning more widespread as software is embedded in ever more devices of daily use.
BibTeX
@inproceedings{dargenio2017is,
  author = {Pedro R. D'Argenio and Gilles Barthe and Sebastian Biewer and Bernd Finkbeiner and Holger Hermanns},
  title = {{Is Your Software on Dope? - Formal Analysis of Surreptitiously "enhanced" Programs}},
  booktitle = {ESOP},
  year = {2017},
  doi = {10.1007/978-3-662-54434-1\_4},
}
Figure