2013
DOI: 10.1007/978-3-642-37288-9_1
|View full text |Cite
|
Sign up to set email alerts
|

Towards the Hardware Accelerated Defensive Virtual Machine – Type and Bound Protection

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2013
2013
2016
2016

Publication Types

Select...
2
2
2

Relationship

2
4

Authors

Journals

citations
Cited by 10 publications
(7 citation statements)
references
References 13 publications
0
7
0
Order By: Relevance
“…This bytecode encryption counteracts the security threat of jumping out of the actual method code and executing undefined data. Another countermeasure proposed in [7,11] counteracts the threat of type confusion between the two main data types integralData and reference. All elements of one main data type are pushed and popped onto their specific OS.…”
Section: Related Workmentioning
confidence: 98%
See 1 more Smart Citation
“…This bytecode encryption counteracts the security threat of jumping out of the actual method code and executing undefined data. Another countermeasure proposed in [7,11] counteracts the threat of type confusion between the two main data types integralData and reference. All elements of one main data type are pushed and popped onto their specific OS.…”
Section: Related Workmentioning
confidence: 98%
“…No Applet Preprocessing Required: In [11,12], a defensive JVM that stores the used main data type integralData or reference during run-time for every OS and LV element are proposed. A drawback of this type of storing approach is that it requires additional memory for type storing and additional computational power for the type checks.…”
Section: Related Workmentioning
confidence: 99%
“…Preventing type confusion from a Java Card applet aims at blocking arithmetic operations on reference. Lackner et al (2012) proposed a typed stack where each element is associated with a bit. During the access of an element, the JCRE checks the associated bit value to avoid a type confusion attack from the Java Card stack.…”
Section: Type Confusion On a Typed Stackmentioning
confidence: 99%
“…Another run-time check against FAs is proposed in [10,14], in which they create separate OSes for each of the two data types, integralValue and reference. With this approach of splitting the OS, it is possible to counteract type-confusion attacks.…”
Section: Countermeasures Against Java Card Attacksmentioning
confidence: 99%
“…With the help of these policies, it is possible to counteract the most dangerous threats that jeopardize security-critical data on the card. The type and bound policies are taken from [14] and are augmented with a control-flow policy. The fulfillment of the three policies on every bytecode is checked by three different D-VM layer implementations using our D-VM API.…”
Section: Security Policymentioning
confidence: 99%