2015
DOI: 10.1007/978-3-319-21690-4_29
|View full text |Cite
|
Sign up to set email alerts
|

Norn: An SMT Solver for String Constraints

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
84
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 69 publications
(84 citation statements)
references
References 9 publications
0
84
0
Order By: Relevance
“…(1) Besides the length bound, on what factors does the running time of counting algorithm depend? (2) Why are the values of α estimated from the experimental results larger than the theoretical result α = 2? For the first question (1), the empirical results show that beside length bound, the size of the input CFG also affects the running time.…”
Section: Basic Performancementioning
confidence: 96%
See 1 more Smart Citation
“…(1) Besides the length bound, on what factors does the running time of counting algorithm depend? (2) Why are the values of α estimated from the experimental results larger than the theoretical result α = 2? For the first question (1), the empirical results show that beside length bound, the size of the input CFG also affects the running time.…”
Section: Basic Performancementioning
confidence: 96%
“…It supports equations, length, substring and replacement as constraints, but does not support regular language containment (membership). More recent tools such as CVC4 [20], S3 [30] and Norn [2] support regular language containment. For example, Norn is based on [1], which provides a sound overapproximation of the strings generated by a Horn-clause program.…”
Section: String Constraint Solvingmentioning
confidence: 99%
“…In recent years, many algorithms for solving string constraints have been developed and implemented in SMT solvers such as Norn [6], CVC4 [12], and Z3 (e.g., Z3str2 [13] and Z3str3 [7]). To validate and benchmark these solvers, their developers have relied on hand-crafted input suites [1,4,5] or real-world examples from a limited set of industrial applications [2,11].…”
Section: Introductionmentioning
confidence: 99%
“…Among them, Stranger, JST, StringGraph, S3, Z3-str2, and CVC4 support the most number of string operations (e.g., startsWith, endsWith, replace, replaceAll, length, and matches) that are essential in the context of vulnerability detection; they also support numeric constraints. Although Hampi and Kaluza have been widely-used as benchmarks for evaluating other solvers (see [7]- [9], [48]), they actually support only a smaller set of string operations than the solvers listed above; also, Hampi does not support numeric constraints. Support for regular expressions (which are usually used in attack specifications) is only provided -often in a limited form -by Sushi, Stranger, ABC, Kaluza, S3, Z3-str2, and CVC4.…”
Section: Related Workmentioning
confidence: 99%
“…There are many constraint solvers that provide, to a certain degree, support for strings: bit-vector based solvers like Hampi [45] and Kaluza [3]; automata-based solvers like Violist [46], Stranger [6], [14], ABC [47], StrSolve [15], Pass [16], StringGraph [17], and JST [18]; word-based solvers like Norn [48], S3 [8], and the aforementioned Sushi, CVC4, and Z3-str2. Among them, Stranger, JST, StringGraph, S3, Z3-str2, and CVC4 support the most number of string operations (e.g., startsWith, endsWith, replace, replaceAll, length, and matches) that are essential in the context of vulnerability detection; they also support numeric constraints.…”
Section: Related Workmentioning
confidence: 99%