Giyeol Kim
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Research Interests
Giyeol Kim has a total of 9 co-authors. Here are the top co-authors by number of shared publications:
- Taegyu Kim
The Pennsylvania State University, University Park, USA
2 shared publications - Changyul Lee
The Pennsylvania State University, University Park, USA
1 shared publication - Daeun Lee
Pusan National University, Busan, Republic of Korea
1 shared publication - Deokjin Kim
The Affiliated Institute of ETRI, Daejeon, Republic of Korea
1 shared publication - Dohyun Ryu
The Pennsylvania State University, State College, PA, USA
1 shared publication - Junghwan Rhee
University of Central Oklahoma
1 shared publication
Latest Publications
- Open Access
- 4 November 2024
- Published by Association for Computing Machinery (ACM)
- p. 450-463
LTA: Control-Driven UAV Testing and Bug Localization with Flight Record Decomposition
As UAVs have been widely used in various domains, such as the military and industry, their safety and security have become crucial. One of their root causes is software bugs, which fall into two bug categories: traditional software bugs, such as memory safety bugs, and UAV-specific logical model-misimplementation (LMM) bugs leading to physical misbehavior, such as crashes. To discover and localize bugs, many proactive and reactive techniques have been proposed. However, LMM bug mitigation techniques are still immature, unlike well-established techniques for traditional software bugs, because existing approaches are unable to track the causal relationship between the LMM bug root cause in software and its resulting physical misbehavior. Specifically, existing proactive approaches require extensive, time-consuming dynamic testing to capture the physical impacts of LMM bug exploitation amidst a vast input space. Conversely, previous reactive approaches are inaccurate because existing work cannot accurately identify the causal relationship between misbehavior and bug-triggering inputs mixed with benign but suspicious inputs. To address the aforementioned problems, we propose LTA, the replay-based proactive LMM bug localization technique for UAVs. This technique encompasses three key strategies: (i) an accident playback-based input generation to narrow down bug-triggering input candidates, (ii) an input and trace decomposition to exclude false-positive bug-triggering inputs, and (iii) a causal analysis to precisely backtrack from bug-triggering inputs to their root causes. We evaluate LTA on PX4 with three models for quadcopters, hexacopters, and VTOL UAVs. As a result, LTA found 72 real accident cases (caused by LMM bugs) obtained from public accident logs and then localized bugs with 100% accuracy.
- 4 November 2024
- Published by Association for Computing Machinery (ACM)
- p. 450-463
Open AccessLTA: Control-Driven UAV Testing and Bug Localization with Flight Record Decomposition
As UAVs have been widely used in various domains, such as the military and industry, their safety and security have become crucial. One of their root causes is software bugs, which fall into two bug categories: traditional software bugs, such as memory safety bugs, and UAV-specific logical model-misimplementation (LMM) bugs leading to physical misbehavior, such as crashes. To discover and localize bugs, many proactive and reactive techniques have been proposed. However, LMM bug mitigation techniques are still immature, unlike well-established techniques for traditional software bugs, because existing approaches are unable to track the causal relationship between the LMM bug root cause in software and its resulting physical misbehavior. Specifically, existing proactive approaches require extensive, time-consuming dynamic testing to capture the physical impacts of LMM bug exploitation amidst a vast input space. Conversely, previous reactive approaches are inaccurate because existing work cannot accurately identify the causal relationship between misbehavior and bug-triggering inputs mixed with benign but suspicious inputs. To address the aforementioned problems, we propose LTA, the replay-based proactive LMM bug localization technique for UAVs. This technique encompasses three key strategies: (i) an accident playback-based input generation to narrow down bug-triggering input candidates, (ii) an input and trace decomposition to exclude false-positive bug-triggering inputs, and (iii) a causal analysis to precisely backtrack from bug-triggering inputs to their root causes. We evaluate LTA on PX4 with three models for quadcopters, hexacopters, and VTOL UAVs. As a result, LTA found 72 real accident cases (caused by LMM bugs) obtained from public accident logs and then localized bugs with 100% accuracy.
- Open Access
- 27 October 2024
- Published by Association for Computing Machinery (ACM)
- p. 807-818
Differential Fuzzing for Data Distribution Service Programs with Dynamic Configuration
Data Distribution Service (DDS) is a distributed network protocol widely used in cyber-physical systems. DDS provides flexible configurations defined in the formal design specification for safety and security. However, DDS programs suffer from both semantic bugs violating design specifications and software implementation bugs. To discover bugs, network protocol fuzzers have focused on testing client-server models by mutating input packets. However, they are unsuitable for fuzzing DDS programs due to a lack of consideration of the DDS-specific features, such as the DDS-specific input spaces (e.g., dynamic network topology formation and QoS and DDS security configurations) and impacts of DDS-specific semantic bugs (e.g., incorrect topology construction). In this paper, we propose DDSFuzz, a fuzzing framework effective for DDS programs by leveraging the DDS-specific features. Specifically, we develop a DDS dynamic network configuration input generator integrated with a customized state-of-the-art packet input mutator. This configuration input generator produces inputs while considering DDS-specific input spaces, DDS topologies, and parameter configurations and dependencies. This scheme enables DDSFuzz to test code that can be executable in certain DDS network configurations. Furthermore, our differential-fuzzing-based bug detector uncovers DDS-specific semantic bugs, built upon DDS-specific APIs and listeners. We evaluate DDSFuzz with three major DDS programs: Fast DDS, Cyclone DDS, and OpenDDS. As a result, DDSFuzz found 20 bugs, and seven CVEs have been assigned. Furthermore, DDSFuzz shows an average of 6.44 times higher code coverage than that of existing fuzzers showing the effectiveness of DDS bug detection.
- 27 October 2024
- Published by Association for Computing Machinery (ACM)
- p. 807-818
Open AccessDifferential Fuzzing for Data Distribution Service Programs with Dynamic Configuration
Data Distribution Service (DDS) is a distributed network protocol widely used in cyber-physical systems. DDS provides flexible configurations defined in the formal design specification for safety and security. However, DDS programs suffer from both semantic bugs violating design specifications and software implementation bugs. To discover bugs, network protocol fuzzers have focused on testing client-server models by mutating input packets. However, they are unsuitable for fuzzing DDS programs due to a lack of consideration of the DDS-specific features, such as the DDS-specific input spaces (e.g., dynamic network topology formation and QoS and DDS security configurations) and impacts of DDS-specific semantic bugs (e.g., incorrect topology construction). In this paper, we propose DDSFuzz, a fuzzing framework effective for DDS programs by leveraging the DDS-specific features. Specifically, we develop a DDS dynamic network configuration input generator integrated with a customized state-of-the-art packet input mutator. This configuration input generator produces inputs while considering DDS-specific input spaces, DDS topologies, and parameter configurations and dependencies. This scheme enables DDSFuzz to test code that can be executable in certain DDS network configurations. Furthermore, our differential-fuzzing-based bug detector uncovers DDS-specific semantic bugs, built upon DDS-specific APIs and listeners. We evaluate DDSFuzz with three major DDS programs: Fast DDS, Cyclone DDS, and OpenDDS. As a result, DDSFuzz found 20 bugs, and seven CVEs have been assigned. Furthermore, DDSFuzz shows an average of 6.44 times higher code coverage than that of existing fuzzers showing the effectiveness of DDS bug detection.