본문

서브메뉴

상세정보

Towards Evaluating the Security Risks of Using Third-Party Components in IoT Firmware.
Towards Evaluating the Security Risks of Using Third-Party Components in IoT Firmware.
Towards Evaluating the Security Risks of Using Third-Party Components in IoT Firmware.

상세정보

자료유형  
 학위논문(국외)
기본표목-개인명  
표제와 책임표시사항  
Towards Evaluating the Security Risks of Using Third-Party Components in IoT Firmware.
발행, 배포, 간사 사항  
발행, 배포, 간사 사항  
Ann Arbor : ProQuest Dissertations & Theses , 2023
    형태사항  
    158 p.
    일반주기  
    Source: Dissertations Abstracts International, Volume: 87-05, Section: A.
    일반주기  
    Advisor: Beyah, Raheem.
    학위논문주기  
    Thesis (Ph.D.)--Georgia Institute of Technology, 2023.
    요약 등 주기  
    요약1.1 Problem StatementThe Internet of Things (IoT) has become an essential part of Internet connectivity and offered great convenience to our daily lives. For instance, router changes the way of surfing the Internet; smart door lock avoids the cumbersome process of door opening; voice assistant (e.g., Amazon Echo and Google Home) enables us to interact with Internet services and other smart devices through voice commands. Second, developers may fail to strictly follow the API specifications when adopting TPCs, resulting in the TPC usage violation problem, which is typically caused by a set of API misuses, e.g., unchecked return value and incorrect invocation sequence. Many previous works have indicated that the API misuse will introduce serious security implications [5, 6, 7, 8, 9, 10]. For instance, the incorrect use of OpenSSL APIs can cause Man-In-The-Middle attacks [11, 12]. To make things worse, vendors may reuse TPCs with known vulnerabilities or misused APIs in different firmware, or call misused APIs multiple times in firmware, leading to aggravated security risks caused by TPCs.
    주제명부출표목-일반주제명  
    주제명부출표목-일반주제명  
    주제명부출표목-일반주제명  
    주제명부출표목-일반주제명  
    주제명부출표목-일반주제명  
    주제명부출표목-일반주제명  
    주제명부출표목-일반주제명  
    부출표목-단체명  
    기본자료저록  
    Dissertations Abstracts International. 87-05A.
    전자적 위치 및 접속  
     원문정보보기

    MARC

     008260219s2023        us  ||||||||||||||c||eng  d
    ■001000017366010
    ■00520260209102913
    ■006m          o    d                
    ■007cr#unu||||||||
    ■020    ▼a9798265406675
    ■035    ▼a(MiAaPQ)AAI32316186
    ■035    ▼a(MiAaPQ)GeorgiaTech72688
    ■040    ▼aMiAaPQ▼cMiAaPQ
    ■0820  ▼a000
    ■1001  ▼aZhao,  Binbin.
    ■24510▼aTowards  Evaluating  the  Security  Risks  of  Using  Third-Party  Components  in  IoT  Firmware.
    ■260    ▼a[S.l.]▼bGeorgia  Institute  of  Technology.  ▼c2023
    ■260  1▼aAnn  Arbor▼bProQuest  Dissertations  &  Theses▼c2023
    ■300    ▼a158  p.
    ■500    ▼aSource:  Dissertations  Abstracts  International,  Volume:  87-05,  Section:  A.
    ■500    ▼aAdvisor:  Beyah,  Raheem.
    ■5021  ▼aThesis  (Ph.D.)--Georgia  Institute  of  Technology,  2023.
    ■520    ▼a1.1  Problem  StatementThe  Internet  of  Things  (IoT)  has  become  an  essential  part  of  Internet  connectivity  and  offered  great  convenience  to  our  daily  lives.  For  instance,  router  changes  the  way  of  surfing  the  Internet;  smart  door  lock  avoids  the  cumbersome  process  of  door  opening;  voice  assistant  (e.g.,  Amazon  Echo  and  Google  Home)  enables  us  to  interact  with  Internet  services  and  other  smart  devices  through  voice  commands.  Second,  developers  may  fail  to  strictly  follow  the  API  specifications  when  adopting  TPCs,  resulting  in  the  TPC  usage  violation  problem,  which  is  typically  caused  by  a  set  of  API  misuses,  e.g.,  unchecked  return  value  and  incorrect  invocation  sequence.  Many  previous  works  have  indicated  that  the  API  misuse  will  introduce  serious  security  implications  [5,  6,  7,  8,  9,  10].  For  instance,  the  incorrect  use  of  OpenSSL  APIs  can  cause  Man-In-The-Middle  attacks  [11,  12].  To  make  things  worse,  vendors  may  reuse  TPCs  with  known  vulnerabilities  or  misused  APIs  in  different  firmware,  or  call  misused  APIs  multiple  times  in  firmware,  leading  to  aggravated  security  risks  caused  by  TPCs.
    ■590    ▼aSchool  code:  0078.
    ■650  4▼aFirmware.
    ■650  4▼aViolations.
    ■650  4▼aSearch  engines.
    ■650  4▼aThird  party.
    ■650  4▼aComputer  science.
    ■650  4▼aInformation  technology.
    ■650  4▼aWeb  studies.
    ■690    ▼a0984
    ■690    ▼a0489
    ■690    ▼a0646
    ■71020▼aGeorgia  Institute  of  Technology.
    ■7730  ▼tDissertations  Abstracts  International▼g87-05A.
    ■790    ▼a0078
    ■791    ▼aPh.D.
    ■792    ▼a2023
    ■793    ▼aEnglish
    ■85640▼uhttp://www.riss.kr/pdu/ddodLink.do?id=T17366010▼nKERIS▼z이  자료의  원문은  한국교육학술정보원에서  제공합니다.

    미리보기

    내보내기

    chatGPT토론

    Ai 추천 관련 도서


      신착도서 더보기
      관련도서 더보기
      최근 3년간 통계입니다.
      SMS 발송 간략정보 이동 상세정보출력

      소장정보

      • 예약
      • 서가에 없는 책 신고
      • 자료배달서비스
      • 나의폴더
      • 우선정리요청
      소장자료
      등록번호 청구기호 소장처 대출가능여부 대출정보
      EM176831 TD   자료대출실(3층) 정리중  정리중 
      마이폴더

      * 대출중인 자료에 한하여 예약이 가능합니다. 예약을 원하시면 예약버튼을 클릭하십시오.

      해당 도서를 다른 이용자가 함께 대출한 도서

      관련도서

      관련 인기도서

      서평쓰기