Combining Structured Static Code Information and Dynamic Symbolic Traces for Software Vulnerability Prediction
Read the paper · doi:10.1145/3597503.3639212
What this paper does with SQLancer
How it was classified
uses infrastructure — no
SQLancer is cited, not used; nothing in the mentions describes reusing its code.
extends technique — no
No technique is extended; the citation is background.
compares with — no
No empirical comparison against SQLancer is reported in the mentions.
describes as state of the art — no
The citation does not characterise SQLancer as the state of the art.
SQLancer publications it cites (1)
Bibliography entries that resolved to a SQLancer publication, or to a paper by one of the project's authors. A sentence citing one of these numbers is a reference to SQLancer even when it never writes the name.
| # | Entry | Matched as |
|---|---|---|
| 71 | ManuelRiggerandZhendongSu.2020. TestingDatabaseEnginesviaPivoted Query Synthesis.. In OSDI, Vol. 20. 667–682. | sqlancer publication · PQS |
Every place it refers to SQLancer (1)
1 sentence, each stored verbatim from the extracted text with where it was found and how. “Citation marker” means the sentence names no tool at all and was reached through a reference number that resolved to a SQLancer publication.
| Id | Sentence | Found by | Where |
|---|---|---|---|
| M1 | These projects contain 35 CVEs reported by independent users, which were also used by prior work [ 69,71]. |
citation marker |
5.3 Comparison on Known CVEs page 9 |