Protect Your Secrets: Understanding and Measuring Data Exposure in VSCode Extensions
Guardado en:
| Publicado en: | arXiv.org (Dec 1, 2024), p. n/a |
|---|---|
| Autor principal: | |
| Otros Autores: | , |
| Publicado: |
Cornell University Library, arXiv.org
|
| Materias: | |
| Acceso en línea: | Citation/Abstract Full text outside of ProQuest |
| Etiquetas: |
Sin Etiquetas, Sea el primero en etiquetar este registro!
|
MARC
| LEADER | 00000nab a2200000uu 4500 | ||
|---|---|---|---|
| 001 | 3138994630 | ||
| 003 | UK-CbPIL | ||
| 022 | |a 2331-8422 | ||
| 035 | |a 3138994630 | ||
| 045 | 0 | |b d20241201 | |
| 100 | 1 | |a Liu, Yue | |
| 245 | 1 | |a Protect Your Secrets: Understanding and Measuring Data Exposure in VSCode Extensions | |
| 260 | |b Cornell University Library, arXiv.org |c Dec 1, 2024 | ||
| 513 | |a Working Paper | ||
| 520 | 3 | |a Recent years have witnessed the emerging trend of extensions in modern Integrated Development Environments (IDEs) like Visual Studio Code (VSCode) that significantly enhance developer productivity. Especially, popular AI coding assistants like GitHub Copilot and Tabnine provide conveniences like automated code completion and debugging. While these extensions offer numerous benefits, they may introduce privacy and security concerns to software developers. However, there is no existing work that systematically analyzes the security and privacy concerns, including the risks of data exposure in VSCode extensions. In this paper, we investigate on the security issues of cross-extension interactions in VSCode and shed light on the vulnerabilities caused by data exposure among different extensions. Our study uncovers high-impact security flaws that could allow adversaries to stealthily acquire or manipulate credential-related data (e.g., passwords, API keys, access tokens) from other extensions if not properly handled by extension vendors. To measure their prevalence, we design a novel automated risk detection framework that leverages program analysis and natural language processing techniques to automatically identify potential risks in VSCode extensions. By applying our tool to 27,261 real-world VSCode extensions, we discover that 8.5\% of them (i.e., 2,325 extensions) are exposed to credential-related data leakage through various vectors, such as commands, user input, and configurations. Our study sheds light on the security challenges and flaws of the extension-in-IDE paradigm and provides suggestions and recommendations for improving the security of VSCode extensions and mitigating the risks of data exposure. | |
| 653 | |a Programming environments | ||
| 653 | |a Visual programming languages | ||
| 653 | |a Security | ||
| 653 | |a Automation | ||
| 653 | |a Privacy | ||
| 653 | |a Natural language processing | ||
| 653 | |a Software development | ||
| 653 | |a Exposure | ||
| 700 | 1 | |a Tantithamthavorn, Chakkrit | |
| 700 | 1 | |a Li, Li | |
| 773 | 0 | |t arXiv.org |g (Dec 1, 2024), p. n/a | |
| 786 | 0 | |d ProQuest |t Engineering Database | |
| 856 | 4 | 1 | |3 Citation/Abstract |u https://www.proquest.com/docview/3138994630/abstract/embedded/ITVB7CEANHELVZIZ?source=fedsrch |
| 856 | 4 | 0 | |3 Full text outside of ProQuest |u http://arxiv.org/abs/2412.00707 |