dc.rights.license | Attribution 4.0 International | |
dc.contributor.author | Santos Grueiro, Igor | |
dc.contributor.other | Llorente-Vazquez, Oscar | |
dc.contributor.other | García Bringas, Pablo | |
dc.date.accessioned | 2024-02-02T08:53:08Z | |
dc.date.available | 2024-02-02T08:53:08Z | |
dc.date.issued | 2023 | |
dc.identifier.issn | 2169-3536 | |
dc.identifier.other | https://katalogoa.mondragon.edu/janium-bin/janium_login_opac.pl?find&ficha_no=172985 | |
dc.identifier.uri | https://hdl.handle.net/20.500.11984/6210 | |
dc.description.abstract | Concurrent programs are widespread in modern systems. They make better use of processor resources but inevitably introduce a new set of problems in terms of reliability and security. Concurrency bugs usually lead to program crashes and unexpected behavior, and are an active research topic. From a security perspective, concurrency vulnerabilities are those that exhibit harmful behavior exclusively in concurrent executions. They can take place in a diverse range of environments, such as in operating system kernels, file system operations, or general-purpose multithreaded programs. A particular characteristic of concurrency is that it not only introduces new problems, but also enables traditional vulnerabilities to be triggered in concurrent-specific ways. Those that lead to dangerous security vulnerabilities usually cause memory corruption, a strong and flexible primitive for exploitation, and are known as concurrency memory corruption vulnerabilities. In this paper, we systematically analyze concurrency vulnerabilities in C and C++ programs, their exploitation and their detection, focusing on concurrency memory corruption vulnerabilities. We organize previous work on concurrency bug characteristics and detection, and highlight the differences in relation to vulnerabilities. Then, we examine the existence of concurrency vulnerabilities in real-world programs by searching the CVE database and point out a growing trend. Further, we analyze and compare existing detection approaches towards concurrency memory corruption. | |
dc.language.iso | eng | |
dc.publisher | IEEE | |
dc.rights | © 2023 The Authors | |
dc.rights.uri | http://creativecommons.org/licenses/by/4.0/ | |
dc.subject | Concurrent computing | |
dc.subject | Instruction sets | |
dc.subject | Computer bugs | |
dc.subject | Testing | |
dc.subject | Programming | |
dc.subject | Behavioral sciences | |
dc.subject | Synchronization | |
dc.title | When Memory Corruption Met Concurrency: Vulnerabilities in Concurrent Programs | |
dcterms.accessRights | http://purl.org/coar/access_right/c_abf2 | |
dcterms.source | IEEE Access | |
local.description.peerreviewed | true | |
local.identifier.doi | https://doi.org/10.1109/ACCESS.2023.3272833 | |
local.contributor.otherinstitution | https://ror.org/00ne6sr39 | |
local.contributor.otherinstitution | HP Labs | |
local.source.details | Vol. 11. Pp. 44725-44740, 2023 | |
oaire.format.mimetype | application/pdf | |
oaire.file | $DSPACE\assetstore | |
oaire.resourceType | http://purl.org/coar/resource_type/c_6501 | |
oaire.version | http://purl.org/coar/version/c_970fb48d4fbd8a85 | |