JACK — A Tool for Validation of Security and Behaviour of Java Applications

Barthe, Gilles; Burdy, Lilian; Charles, Julien; Grégoire, Benjamin; Huisman, Marieke; Lanet, Jean‐Louis; Pavlova, Mariela; Requet, A

doi:10.1007/978-3-540-74792-5_7

Cited by 25 publications

(22 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Neither the checker nor any example output is publicly available, so it is difficult to compare to our work. Other frameworks that could be used for writing pluggable type systems include JastAdd [9], JACK [5], and Polyglot [18].…”

Section: Related Workmentioning

confidence: 99%

Inference of Reference Immutability

Quinonez¹,

Tschantz²,

Ernst³

ECOOP 2008 – Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. Javari is an extension of Java that supports reference immutability constraints. Programmers write readonly type qualifiers and other constraints, and the Javari typechecker detects mutation errors (incorrect side effects) or verifies their absence. While case studies have demonstrated the practicality and value of Javari, a barrier to usability remains. A Javari program will not typecheck unless all the references in the APIs of libraries it uses are annotated with Javari type qualifiers. Manually converting existing Java libraries to Javari is tedious and error-prone. We present an algorithm for inferring reference immutability in Javari. The flow-insensitive and context-sensitive algorithm is sound and produces a set of qualifiers that typecheck in Javari. The algorithm is precise in that it infers the most readonly qualifiers possible; adding any additional readonly qualifiers will cause the program to not typecheck. We have implemented the algorithm in a tool, Javarifier, that infers the Javari type qualifiers over a set of class files. Javarifier automatically converts Java libraries to Javari. Additionally, Javarifier eases the task of converting legacy programs to Javari by inferring the mutability of every reference in a program. In case studies, Javarifier correctly inferred mutability over Java programs of up to 110 KLOC.

show abstract

Section: Related Workmentioning

confidence: 99%

Inference of Reference Immutability

Quinonez¹,

Tschantz²,

Ernst³

ECOOP 2008 – Object-Oriented Programming

View full text Add to dashboard Cite

show abstract

“…As before, the presented framework does not feature any static analysis. JACK [4] is a tool for the validation of Java applications, both at the levels of bytecode and of source code. Programmers specify application properties through JML annotations, which are equi-expressive with first-order logics.…”

Section: Static Analysis and Optimizationsmentioning

confidence: 99%

Securing Java with Local Policies.

Bartoletti¹,

Costa²,

Degano³

et al. 2009

JOT

View full text Add to dashboard Cite

Abstract. We propose an extension to the security model of Java. It allows for specifying, analysing and enforcing history-based policies. Policies are defined by finite state automata recognizing the permitted execution histories. Programmers can sandbox an untrusted piece of code with a policy, which is enforced at run-time through its local scope. A static analysis allows for optimizing the execution monitor, that will only check the program points where some security violation may actually occur.

show abstract

“…For this program, manual code inspection to reveal whether a JML error was hidden might not be straightforward (remember that the code for the decrypt method and the invocation of sneakyMethod might be stored in different classes). Naturally, tools for static validation of JML annotations (such as ESC/Java [5] or Jack [2]) would detect this attempt to call decrypt with illegal arguments.…”

Section: Examplesmentioning

confidence: 99%

On the interplay between the semantics of Java's finally clauses and the JML run-time checker

Huisman

2009

Proceedings of the 11th International Workshop on Formal Techniques for Java-Like Programs

View full text Add to dashboard Cite

This paper discusses how a subtle interaction between the semantics of Java and the implementation of the JML runtime checker can cause the latter to fail to report errors. This problem is due to the well-known capability of finally clauses to implicitly override exceptions. We give some simple examples of annotation violations that are not reported by the run-time checker because the errors are caught within the program text; even without any explicit reference to them. We explain this behaviour, based on the official Java Language Specification. We also discuss what are the consequences of this problem, and we sketch different solutions to the problem (by adapting the implementation of the JML run-time checker, or by adopting a slightly different semantics for Java).

show abstract

JACK — A Tool for Validation of Security and Behaviour of Java Applications

Cited by 25 publications

References 22 publications

Inference of Reference Immutability

Inference of Reference Immutability

Securing Java with Local Policies.

On the interplay between the semantics of Java's finally clauses and the JML run-time checker

Contact Info

Product

Resources

About