UNGOML: Automated Classification of unsafe Usages in Go

June 01, 2023 Β· Entered Twilight Β· πŸ› IEEE Working Conference on Mining Software Repositories

πŸ’€ TWILIGHT: Eternal Rest
Repo abandoned since publication

Repo contents: .gitignore, .gitmodules, .vscode, Dockerfile, LICENSE, README.md, __init__,py, dummy_project, evaluate.py, gfx, requirements.txt, run.py, snippet.go, tests.py, unsafe-go-classifier, visualize.py

Authors Anna-Katharina Wickert, Clemens Damke, Lars BaumgÀrtner, Eyke Hüllermeier, Mira Mezini arXiv ID 2306.00694 Category cs.SE: Software Engineering Cross-listed cs.CR Citations 1 Venue IEEE Working Conference on Mining Software Repositories Repository https://github.com/stg-tud/ungoml ⭐ 8 Last Checked 3 months ago
Abstract
The Go programming language offers strong protection from memory corruption. As an escape hatch of these protections, it provides the unsafe package. Previous studies identified that this unsafe package is frequently used in real-world code for several purposes, e.g., serialization or casting types. Due to the variety of these reasons, it may be possible to refactor specific usages to avoid potential vulnerabilities. However, the classification of unsafe usages is challenging and requires the context of the call and the program's structure. In this paper, we present the first automated classifier for unsafe usages in Go, UNGOML, to identify what is done with the unsafe package and why it is used. For UNGOML, we built four custom deep learning classifiers trained on a manually labeled data set. We represent Go code as enriched control-flow graphs (CFGs) and solve the label prediction task with one single-vertex and three context-aware classifiers. All three context-aware classifiers achieve a top-1 accuracy of more than 86% for both dimensions, WHAT and WHY. Furthermore, in a set-valued conformal prediction setting, we achieve accuracies of more than 93% with mean label set sizes of 2 for both dimensions. Thus, UNGOML can be used to efficiently filter unsafe usages for use cases such as refactoring or a security audit. UNGOML: https://github.com/stg-tud/ungoml Artifact: https://dx.doi.org/10.6084/m9.figshare.22293052
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering