2015
DOI: 10.1007/s11416-015-0251-1
|View full text |Cite
|
Sign up to set email alerts
|

Buffer overflow vulnerabilities in CUDA: a preliminary analysis

Abstract: We present a preliminary study of buffer overflow vulnerabilities in CUDA software running on GPUs. We show how an attacker can overrun a buffer to corrupt sensitive data or steer the execution flow by overwriting function pointers, e.g., manipulating the virtual table of a C++ object. In view of a potential mass market diffusion of GPU accelerated software this may be a major concern.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
10
0

Year Published

2016
2016
2024
2024

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 25 publications
(10 citation statements)
references
References 3 publications
0
10
0
Order By: Relevance
“…Miele [31] discusses ways of causing stack and heap overflows for corrupting sensitive data or changing the execution flow. They discuss two attacks.…”
Section: Buffer Overflow Attackmentioning
confidence: 99%
“…Miele [31] discusses ways of causing stack and heap overflows for corrupting sensitive data or changing the execution flow. They discuss two attacks.…”
Section: Buffer Overflow Attackmentioning
confidence: 99%
“…It is worth noting that the line 12 is only executed in the malicious kernel to initialize the overf buffer. If we set length to 26 and initialize overf with the value 0x590 (address of the malicious function that can be obtained using printf("%p",malicious) or CUDA-GDB [5]), the output at line 18 would be string "Normal". This is because with value 26, we can only overwrite the first 5 pointers in fp (sizeof(buf ) + sizeof(pFdummy) * 5 == 26 ).…”
Section: Stack Overflowmentioning
confidence: 99%
“…However, setting length to 27 would cause the output at line 18 to be "Attack! ", indicating that fp [5] is successfully overwritten by the address of the malicious function. This example demonstrates that current GPUs have no mechanisms to prevent stack overflow like stack canaries on the CPU counterpart.…”
Section: Stack Overflowmentioning
confidence: 99%
See 2 more Smart Citations