Proceedings of the First Workshop on Cryptography and Security in Computing Systems 2014
DOI: 10.1145/2556315.2556317
|View full text |Cite
|
Sign up to set email alerts
|

Countering type confusion and buffer overflow attacks on Java smart cards by data type sensitive obfuscation

Abstract: Java enabled smart cards protect security-related code and data by a sandbox concept. Unfortunately, this sandbox can be bypassed by fault attacks. Therefore, there is a substantial need for transparent, effective, and low-overhead countermeasures. This work demonstrates a new countermeasure against type confusion and buffer overflow attacks. This new countermeasure is based on obfuscating the security critical calculation parts of a virtual machine by secret keys. This countermeasure was integrated into a Jav… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(2 citation statements)
references
References 16 publications
0
2
0
Order By: Relevance
“…These hardware blocks aim at protecting the runtime environment. Lackner et al designed mitigation to prevent type confusion onto the stack [24,25] and the heap [8]. In his master's thesis, Zelle [46] describes how to protect the Java Card firewall through a Memory Protection Unit (MPU).…”
Section: Related Workmentioning
confidence: 99%
“…These hardware blocks aim at protecting the runtime environment. Lackner et al designed mitigation to prevent type confusion onto the stack [24,25] and the heap [8]. In his master's thesis, Zelle [46] describes how to protect the Java Card firewall through a Memory Protection Unit (MPU).…”
Section: Related Workmentioning
confidence: 99%
“…Consequently, numerous studies on obfuscation have turned to quantitative measures when evaluating their techniques. These studies primarily utilize metrics like McCabe cyclomatic complexity [16,12,17,13,18], Line of Code (LoC) [12,[19][20][21], and runtime overhead [9,[22][23][24][25][26]. Nonetheless, there are limitations to assessing obfuscation quality when just a single or a small number of evaluation indicators are used.…”
Section: Introductionmentioning
confidence: 99%