Value-Based Constraint Control Flow Integrity

Cited 4 time in webofscience Cited 3 time in scopus
  • Hit : 651
  • Download : 361
DC FieldValueLanguage
dc.contributor.authorJung, Dongjaeko
dc.contributor.author김민수ko
dc.contributor.authorJang, Jinsooko
dc.contributor.authorKang, Brent Byunghoonko
dc.date.accessioned2020-04-29T03:20:04Z-
dc.date.available2020-04-29T03:20:04Z-
dc.date.created2020-04-27-
dc.date.created2020-04-27-
dc.date.created2020-04-27-
dc.date.issued2020-03-
dc.identifier.citationIEEE ACCESS, v.8, pp.50531 - 50542-
dc.identifier.issn2169-3536-
dc.identifier.urihttp://hdl.handle.net/10203/274044-
dc.description.abstractControl flow integrity (CFI) is a generic technique that prevents a control flow hijacking attacks by verifying the legitimacy of indirect branches against a predefined set of targets. State-of-the-art CFI solutions focus on reducing the number of targets using the context of a program such as the path to the indirect branch and the origin of the code pointer. However, these solutions work with an impractical assumption that the attacker only compromises control data; non-control data such as condition data that can also be abused by attackers are not considered. To overcome these limitations, in this paper, we propose value-based constraint CFI (vCFI) to improve the effectiveness of CFI by retrieving and protecting all data that can potentially be manipulated for control flow hijacking. We first perform static analysis such as dependency, condition, and data analyses to derive all control flow-related data. Then, vCFI protects these data during runtime by instrumenting a program to be hardened. We implemented vCFI as a compiler extension and evaluated its performance using SPEC CPU2006. The performance degradation caused by adopting vCFI was reasonable, and the average overhead was 13.6 & x0025;.-
dc.languageEnglish-
dc.publisherIEEE-INST ELECTRICAL ELECTRONICS ENGINEERS INC-
dc.titleValue-Based Constraint Control Flow Integrity-
dc.typeArticle-
dc.identifier.wosid000524898700029-
dc.identifier.scopusid2-s2.0-85082394551-
dc.type.rimsART-
dc.citation.volume8-
dc.citation.beginningpage50531-
dc.citation.endingpage50542-
dc.citation.publicationnameIEEE ACCESS-
dc.identifier.doi10.1109/ACCESS.2020.2980026-
dc.contributor.localauthorKang, Brent Byunghoon-
dc.description.isOpenAccessY-
dc.type.journalArticleArticle-
dc.subject.keywordAuthorRuntime-
dc.subject.keywordAuthorHardware-
dc.subject.keywordAuthorStatic analysis-
dc.subject.keywordAuthorData models-
dc.subject.keywordAuthorInstruments-
dc.subject.keywordAuthorControl flow hijacking-
dc.subject.keywordAuthorcontrol flow integrity-
dc.subject.keywordAuthornon-control data-
dc.subject.keywordAuthorprogram analysis-
This item is cited by other documents in WoS
⊙ Detail Information in WoSⓡ Click to see webofscience_button
⊙ Cited 4 items in WoS Click to see citing articles in records_button

qr_code

  • mendeley

    citeulike


rss_1.0 rss_2.0 atom_1.0