2014
DOI: 10.15514/ispras-2014-26(1)-7
|View full text |Cite
|
Sign up to set email alerts
|

Static analyzer Svace for finding of defects in program source code

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
1
0
1

Year Published

2015
2015
2019
2019

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 13 publications
(2 citation statements)
references
References 1 publication
0
1
0
1
Order By: Relevance
“…Thus, the path along which a leak occurs is as follows: 7 -9 -11 -9 -12 -4 -12 -9 -13. The static analysis tool Svace developed at the Institute for System Programming, RAS, performs taint analysis aimed at detecting vulnerabilities of type "use of unchecked input data" [1]. Currently, Svace uses general purpose analysis infrastructure that sup ports a wide class of checks.…”
Section: Survey Of the Existing Approaches To Taint Analysismentioning
confidence: 99%
“…Thus, the path along which a leak occurs is as follows: 7 -9 -11 -9 -12 -4 -12 -9 -13. The static analysis tool Svace developed at the Institute for System Programming, RAS, performs taint analysis aimed at detecting vulnerabilities of type "use of unchecked input data" [1]. Currently, Svace uses general purpose analysis infrastructure that sup ports a wide class of checks.…”
Section: Survey Of the Existing Approaches To Taint Analysismentioning
confidence: 99%
“…Размещение в стеке перед адресом возврата специального значения «канарейки», призванного выявлять ошибки переполнение буфера на стеке, не защищает от уязвимости форматной строки, так как перезаписывается не диапазон адресов памяти, а только адрес возврата. Поиск ошибок и уязвимостей можно проводить как на уровне исходных текстов [2], так и в бинарном коде [3]. Поиск ошибок на уровне бинарного кода имеет преимущества не только, когда исходные тексты исследуемого ПО недоступны.…”
Section: Introductionunclassified