Ghosts in DBMS: Revealing the Security Impacts of Silent Fixes
Read the paper · doi:10.1007/978-981-95-3182-0_3
What this paper does with SQLancer
How it was classified
uses infrastructure — no
SQLancer is cited as related work; no reuse of its code, generator or workload is described.
extends technique — no
No SQLancer technique is extended; the citation is background.
compares with — no
No empirical comparison against SQLancer or one of its oracles is reported.
describes as state of the art — no
The text does not describe SQLancer as the state of the art.
SQLancer publications it cites (3)
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 |
|---|---|---|
| 38 | Rigger, M., Su, Z.: Finding bugs in database systems via query partitioning. Proc. 35th ACM Program. Lang. (OOPSLA) 4, 1–30 (2020) | sqlancer publication · TLP |
| 40 | Jiang, Y., Liu, J., Ba, J., Yap, R.H., Liang, Z., Rigger, M.: Detecting logic bugs in graph database management systems via injective and surjective graph query transformation. In: Proceedings of the 46th IEEE/ACM Int... | project authored |
| 43 | Fu, J., Liang, J., Wu, Z., Zhao, Y., Li, S., Jiang, Y.: Understanding and detecting sql function bugs: using simple boundary arguments to trigger hundreds of dbms bugs. In: Proceedings of the 20th European Conference ... | project authored |
Every place it refers to SQLancer (2)
2 sentences, 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 | Prior efforts have addressed such issues using query partitioning [ 38], validity-guided fuzzing [ 39], graph-based query transformations [ 40], and syntax abstraction frameworks [ 41]. |
technique |
6 Related Works page 16 |
| M2 | Besides, DBMSs suffer from domain-specific vulnerabilities such as transaction anomalies [ 42], where real-world cases compromise consistency guarantees, and flaws in built-in SQL functions [ 43]. | citation marker project authored | 6 Related Works page 16 |