Understanding security mistakes developers make: Qualitative analysis from Build It, Break It, Fix It
By Daniel Votipka, Kelsey R. Fulton, James Parker, Matthew Hou, Michelle L. Mazurek, Michael W. Hicks. 2020
86 citations recorded by the source corpus.
Subfields: Safety, Robustness & Interpretability
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Safety, Robustness & Interpretability
- Congzheng Song
- Vitaly Shmatikov
- Roei Schuster
- Eran Tromer
- Reza Shokri
- Prateek Mittal
- Liwei Song
- Yang Zhang
Citations in the corpus
- You Autocomplete Me: Poisoning Vulnerabilities in Neural Code Completion (2020, methodology): “Despite its insecurity, ECB is still used by programmers [20, 63].”
- Do Users Write More Insecure Code with AI Assistants? (2022, unknown): “• Correct if it can encrypt/decrypt messages of any length • Partially Correct if this condition holds only for messages of • Incorrect if this condition does not hold”
- Fix that Fix Commit: A real-world remediation analysis of JavaScript projects (2020, background): “Prior work has looked into writing secure code and getting security to advise on the web [23], [25].”