Martin, Kayondo
(Department of Electrical and Computer Engineering and Inter-University Semiconductor Research Center, Seoul National University)
,
Bang, In-Young
(Department of Electrical and Computer Engineering and Inter-University Semiconductor Research Center, Seoul National University)
,
You, Jun-Seung
(Department of Electrical and Computer Engineering and Inter-University Semiconductor Research Center, Seoul National University)
,
Seo, Ji-Won
(Department of Electrical and Computer Engineering and Inter-University Semiconductor Research Center, Seoul National University)
,
Paek, Yun-Heung
(Department of Electrical and Computer Engineering and Inter-University Semiconductor Research Center, Seoul National University)
Rust is a promising system programming language that made its debut in 2010. It was developed to address the security problems in C/C++. It features a property called ownership, on which it relies to mitigate memory attacks. For this and its many other features, the language has consistently gained ...
Rust is a promising system programming language that made its debut in 2010. It was developed to address the security problems in C/C++. It features a property called ownership, on which it relies to mitigate memory attacks. For this and its many other features, the language has consistently gained popularity and many companies have begun to seriously consider it for production uses. However, Rust also supports safe and unsafe regions under which the foreign function interface (FFI), used to port to other languages, falls. In the unsafety region, Rust surrenders most of its safety features, allowing programmers to perform operations without check. In this study, we analyze the security issues that arise due to Rust's safety/unsafety property, especially those introduced by Rust FFI.
Rust is a promising system programming language that made its debut in 2010. It was developed to address the security problems in C/C++. It features a property called ownership, on which it relies to mitigate memory attacks. For this and its many other features, the language has consistently gained popularity and many companies have begun to seriously consider it for production uses. However, Rust also supports safe and unsafe regions under which the foreign function interface (FFI), used to port to other languages, falls. In the unsafety region, Rust surrenders most of its safety features, allowing programmers to perform operations without check. In this study, we analyze the security issues that arise due to Rust's safety/unsafety property, especially those introduced by Rust FFI.
※ AI-Helper는 부적절한 답변을 할 수 있습니다.