Cited 0 time in
A Dynamically Linked Library Based Indirect Call Function Analysis for Detecting Banned API Usage in Binary Code
| DC Field | Value | Language |
|---|---|---|
| dc.contributor.author | Jeong, Junho | - |
| dc.contributor.author | Son, Yunsik | - |
| dc.date.accessioned | 2023-04-28T09:41:35Z | - |
| dc.date.available | 2023-04-28T09:41:35Z | - |
| dc.date.issued | 2018-03 | - |
| dc.identifier.issn | 2005-4262 | - |
| dc.identifier.uri | https://scholarworks.dongguk.edu/handle/sw.dongguk/9716 | - |
| dc.description.abstract | The use of Inherently Dangerous Function could cause vulnerabilities in a program which makes it disadvantageous. If the source code exits, this problem can easily be solved by simply removing the use of dangerous functions based on the list of prohibited functions. However, if only the binary code exits, it is difficult to analyze the list of functions used in the code. Furthermore, it is challenging to understand the information of functions used in analysis, such as reverse engineering, because a lot of the information in library functions that are linked dynamically in a typical binary file has been removed. In this paper, we propose a method to find indirectly called function information by using the information when calling a function in binary code based on indirect calling method used in the windows environment. | - |
| dc.format.extent | 10 | - |
| dc.language | 영어 | - |
| dc.language.iso | ENG | - |
| dc.publisher | SERSC | - |
| dc.title | A Dynamically Linked Library Based Indirect Call Function Analysis for Detecting Banned API Usage in Binary Code | - |
| dc.type | Article | - |
| dc.publisher.location | 호주 | - |
| dc.identifier.doi | 10.14257/ijgdc.2018.11.3.07 | - |
| dc.identifier.scopusid | 2-s2.0-85045009846 | - |
| dc.identifier.bibliographicCitation | International Journal of Grid and Distributed Computing, v.11, no.3, pp 79 - 88 | - |
| dc.citation.title | International Journal of Grid and Distributed Computing | - |
| dc.citation.volume | 11 | - |
| dc.citation.number | 3 | - |
| dc.citation.startPage | 79 | - |
| dc.citation.endPage | 88 | - |
| dc.type.docType | Article | - |
| dc.description.isOpenAccess | N | - |
| dc.description.journalRegisteredClass | scopus | - |
| dc.description.journalRegisteredClass | esci | - |
| dc.relation.journalResearchArea | Computer Science | - |
| dc.relation.journalWebOfScienceCategory | Computer Science, Software Engineering | - |
| dc.subject.keywordPlus | SECURITY | - |
| dc.subject.keywordAuthor | Code Analysis | - |
| dc.subject.keywordAuthor | Indirect Call | - |
| dc.subject.keywordAuthor | Vulnerable function | - |
| dc.subject.keywordAuthor | Secure Software | - |
Items in ScholarWorks are protected by copyright, with all rights reserved, unless otherwise indicated.
30, Pildong-ro 1-gil, Jung-gu, Seoul, 04620, Republic of Korea+82-2-2260-3114
Copyright(c) 2023 DONGGUK UNIVERSITY. ALL RIGHTS RESERVED.
Certain data included herein are derived from the © Web of Science of Clarivate Analytics. All rights reserved.
You may not copy or re-distribute this material in whole or in part without the prior written consent of Clarivate Analytics.
