Publications
2021
Lama J Moukahal; Mohammad Zulkernine; Martin Soukup
Boosting Grey-box Fuzzing for Connected Autonomous Vehicle Systems Conference Forthcoming
2021 IEEE International Symposium on Autonomous Vehicle Software (IEEE AVS 2021), IEEE, Forthcoming.
@conference{nokey,
title = {Boosting Grey-box Fuzzing for Connected Autonomous Vehicle Systems},
author = {Lama J Moukahal and Mohammad Zulkernine and Martin Soukup},
year = {2021},
date = {2021-11-15},
booktitle = {2021 IEEE International Symposium on Autonomous Vehicle Software (IEEE AVS 2021)},
publisher = {IEEE},
keywords = {},
pubstate = {forthcoming},
tppubtype = {conference}
}
Lama J Moukahal; Mohammad Zulkernine; Martin Soukup
Vulnerability-Oriented Fuzz Testing for Connected Autonomous Vehicle Systems Journal Article
In: IEEE Transactions on Reliability (ToR), 70 (4), pp. 1422-1437, 2021, ISSN: 1558-1721.
@article{VulOrientedFuzzTest,
title = {Vulnerability-Oriented Fuzz Testing for Connected Autonomous Vehicle Systems},
author = {Lama J Moukahal and Mohammad Zulkernine and Martin Soukup},
url = {https://ieeexplore.ieee.org/document/9557794},
doi = {10.1109/TR.2021.3112538},
issn = {1558-1721},
year = {2021},
date = {2021-10-04},
urldate = {2021-10-04},
journal = {IEEE Transactions on Reliability (ToR)},
volume = {70},
number = {4},
pages = {1422-1437},
publisher = {IEEE},
abstract = {In an era of connectivity and automation, the vehicle industry is adopting numerous technologies to transform driver-centric vehicles into intelligent mechanical devices driven by software components. Software integration and network connectivity inherit numerous security issues that open the door for malicious attacks. Software security testing is a scalable and practical approach to identify systems’ weaknesses and vulnerabilities at an early stage and throughout their life-cycle. Security specialists recommend fuzz testing to identify vulnerabilities within vehicle software systems. Nevertheless, the randomness and blindness of fuzzing hinder it from becoming a reliable security tool. This article presents a vulnerability-oriented fuzz (VulFuzz) testing framework that utilizes security vulnerability metrics designed particularly for connected and autonomous vehicles to direct and prioritize the fuzz testing toward the most vulnerable components. While most gray-box fuzzing techniques aim solely to expand code coverage, the proposed approach assigns weights to ensure a thorough examination of the most vulnerable components. Moreover, we employ an input structure-aware mutation technique that can bypass vehicle software systems’ input formats to boost test performance and avoid dropped test cases. Such a testing technique will contribute to the quality assurance of vehicle software engineering. We implemented the proposed approach on OpenPilot, a driver assistance system, and compared our results to American fuzzy lop (AFL) and an unguided mutation-based fuzzer. Within 16.8 h, VulFuzz exposed 335 crashes, 41 times more than AFL and two times more than an unguided mutation-based fuzzer. VulFuzz is explicitly efficient for automotive systems, reaching the same code coverage as AFL but with more exposed crashes and fewer dropped messages.},
keywords = {},
pubstate = {published},
tppubtype = {article}
}
In an era of connectivity and automation, the vehicle industry is adopting numerous technologies to transform driver-centric vehicles into intelligent mechanical devices driven by software components. Software integration and network connectivity inherit numerous security issues that open the door for malicious attacks. Software security testing is a scalable and practical approach to identify systems’ weaknesses and vulnerabilities at an early stage and throughout their life-cycle. Security specialists recommend fuzz testing to identify vulnerabilities within vehicle software systems. Nevertheless, the randomness and blindness of fuzzing hinder it from becoming a reliable security tool. This article presents a vulnerability-oriented fuzz (VulFuzz) testing framework that utilizes security vulnerability metrics designed particularly for connected and autonomous vehicles to direct and prioritize the fuzz testing toward the most vulnerable components. While most gray-box fuzzing techniques aim solely to expand code coverage, the proposed approach assigns weights to ensure a thorough examination of the most vulnerable components. Moreover, we employ an input structure-aware mutation technique that can bypass vehicle software systems’ input formats to boost test performance and avoid dropped test cases. Such a testing technique will contribute to the quality assurance of vehicle software engineering. We implemented the proposed approach on OpenPilot, a driver assistance system, and compared our results to American fuzzy lop (AFL) and an unguided mutation-based fuzzer. Within 16.8 h, VulFuzz exposed 335 crashes, 41 times more than AFL and two times more than an unguided mutation-based fuzzer. VulFuzz is explicitly efficient for automotive systems, reaching the same code coverage as AFL but with more exposed crashes and fewer dropped messages.
Lama J Moukahal; Mohammad Zulkernine; Martin Soukup
Towards a Secure Software Lifecycle for Autonomous Vehicles Conference Forthcoming
The 32nd International Symposium on Software Reliability Engineering (ISSRE), IEEE, Forthcoming, (Nominated for the Best Industry Paper Award).
@conference{moukahal2021securityVul,
title = {Towards a Secure Software Lifecycle for Autonomous Vehicles},
author = {Lama J Moukahal and Mohammad Zulkernine and Martin Soukup},
year = {2021},
date = {2021-01-01},
urldate = {2021-01-01},
booktitle = {The 32nd International Symposium on Software Reliability Engineering (ISSRE)},
publisher = {IEEE},
note = {Nominated for the Best Industry Paper Award},
keywords = {},
pubstate = {forthcoming},
tppubtype = {conference}
}
Lama J Moukahal; Mohammad Zulkernine; Martin Soukup
AVSDA: Autonomous Vehicle Security Decay Assessment Conference Forthcoming
The 16th International Conference on Risks and Security of Internet and Systems (CRISIS), Springer, Forthcoming.
@conference{moukahal2021AVSDA,
title = {AVSDA: Autonomous Vehicle Security Decay Assessment},
author = {Lama J Moukahal and Mohammad Zulkernine and Martin Soukup},
year = {2021},
date = {2021-01-01},
urldate = {2021-01-01},
booktitle = {The 16th International Conference on Risks and Security of Internet and Systems (CRISIS)},
publisher = {Springer},
keywords = {},
pubstate = {forthcoming},
tppubtype = {conference}
}
2020
Lama J Moukahal; Marwa A Elsayed; Mohammad Zulkernine
Vehicle Software Engineering (VSE): Research and Practice Journal Article
In: IEEE Internet of Things Journal, 7 (10), pp. 10137–10149, 2020, ISSN: 2327-4662.
@article{moukahal2020vehicle,
title = {Vehicle Software Engineering (VSE): Research and Practice},
author = {Lama J Moukahal and Marwa A Elsayed and Mohammad Zulkernine},
url = {https://ieeexplore.ieee.org/document/9112168},
doi = {10.1109/JIOT.2020.3001026},
issn = {2327-4662},
year = {2020},
date = {2020-01-01},
urldate = {2020-01-01},
journal = {IEEE Internet of Things Journal},
volume = {7},
number = {10},
pages = {10137--10149},
publisher = {IEEE},
abstract = {The Internet of Things (IoT) is shaping the future of the automotive industry. Grounded on the advances in everything from sensors, electronic controllers, artificial intelligence, data analytics, to network connectivity, intelligent connected autonomous vehicles (CAVs) have become the essence in IoT applications. The software in CAVs lies at the core of this digital transformation. Faulty software remains the main reason behind the vast number of safety recalls and reputation damage witnessed recently in the automotive industry. The uniqueness of CAVs originates challenges for vehicle software engineering (VSE) that render traditional models and practical solutions for software development ineffective and inapplicable. Despite the raised necessity to adopt a software engineering model that can handle these challenges, there is a lack of studies recognizing the importance of VSE. This article presents an in-depth and comprehensive analysis to perceive the existing software engineering processes detailing their strengths and limitations in the context of CAVs. It also reviews current practical software solutions, including standards, tools, languages, and research efforts to understand the evolution, trends, and current practice in this article area. This article will enable automakers and software providers to better assess and differentiate among the existing software engineering processes and current practical solutions for vehicle software system development. Hence, they would be able to adopt a VSE model and follow best practices that can better meet their challenging needs.},
keywords = {},
pubstate = {published},
tppubtype = {article}
}
The Internet of Things (IoT) is shaping the future of the automotive industry. Grounded on the advances in everything from sensors, electronic controllers, artificial intelligence, data analytics, to network connectivity, intelligent connected autonomous vehicles (CAVs) have become the essence in IoT applications. The software in CAVs lies at the core of this digital transformation. Faulty software remains the main reason behind the vast number of safety recalls and reputation damage witnessed recently in the automotive industry. The uniqueness of CAVs originates challenges for vehicle software engineering (VSE) that render traditional models and practical solutions for software development ineffective and inapplicable. Despite the raised necessity to adopt a software engineering model that can handle these challenges, there is a lack of studies recognizing the importance of VSE. This article presents an in-depth and comprehensive analysis to perceive the existing software engineering processes detailing their strengths and limitations in the context of CAVs. It also reviews current practical software solutions, including standards, tools, languages, and research efforts to understand the evolution, trends, and current practice in this article area. This article will enable automakers and software providers to better assess and differentiate among the existing software engineering processes and current practical solutions for vehicle software system development. Hence, they would be able to adopt a VSE model and follow best practices that can better meet their challenging needs.
2019
Lama Moukahal; Mohammad Zulkernine
Security vulnerability metrics for connected vehicles Conference
2019 IEEE 19th International Conference on Software Quality, Reliability and Security Companion (QRS-C), IEEE, 2019, ISBN: 978-1-7281-3926-5.
@conference{moukahal2019security,
title = {Security vulnerability metrics for connected vehicles},
author = {Lama Moukahal and Mohammad Zulkernine},
url = {https://ieeexplore.ieee.org/document/8859489},
doi = {10.1109/QRS-C.2019.00017},
isbn = {978-1-7281-3926-5},
year = {2019},
date = {2019-01-01},
urldate = {2019-01-01},
booktitle = {2019 IEEE 19th International Conference on Software Quality, Reliability and Security Companion (QRS-C)},
pages = {17--23},
publisher = {IEEE},
abstract = {Software integration in modern vehicles is continuously expanding. This is due to the fact that vehicle manufacturers are always trying to enhance and add more innovative and competitive features that may rely on complex software functionalities. However, these features come at a cost. They amplify the security vulnerabilities in vehicles and lead to more security issues in today's automobiles. As a result, the need for identifying vulnerable components in a vehicle software system has become crucial. Security experts need to know which components of the vehicle software system can be exploited for attacks and should focus their testing and inspection efforts on it. Nevertheless, it is a challenging and costly task to identify these weak components in a vehicle's system. In this paper, we propose some security vulnerability metrics for connected vehicles that aim to assist software testers during the development life-cycle in order to identify the frail links that put the vehicle at highsecurity risks. Vulnerable function assessment can give software testers a good idea about which components in a connected vehicle need to be prioritized in order to mitigate the risk and hence secure the vehicle. The proposed metrics were applied to OpenPilot - a software that provides Autopilot feature - and has been integrated with 48 different vehicles.. The application shows how the defined metrics can be effectively used to quantitatively measure the vulnerabilities of a vehicle software system.},
keywords = {},
pubstate = {published},
tppubtype = {conference}
}
Software integration in modern vehicles is continuously expanding. This is due to the fact that vehicle manufacturers are always trying to enhance and add more innovative and competitive features that may rely on complex software functionalities. However, these features come at a cost. They amplify the security vulnerabilities in vehicles and lead to more security issues in today's automobiles. As a result, the need for identifying vulnerable components in a vehicle software system has become crucial. Security experts need to know which components of the vehicle software system can be exploited for attacks and should focus their testing and inspection efforts on it. Nevertheless, it is a challenging and costly task to identify these weak components in a vehicle's system. In this paper, we propose some security vulnerability metrics for connected vehicles that aim to assist software testers during the development life-cycle in order to identify the frail links that put the vehicle at highsecurity risks. Vulnerable function assessment can give software testers a good idea about which components in a connected vehicle need to be prioritized in order to mitigate the risk and hence secure the vehicle. The proposed metrics were applied to OpenPilot - a software that provides Autopilot feature - and has been integrated with 48 different vehicles.. The application shows how the defined metrics can be effectively used to quantitatively measure the vulnerabilities of a vehicle software system.
2016
Ramzi A Haraty; Nashat Mansour; Lama Moukahal; Iman Khalil
Regression Test Cases Prioritization Using Clustering and Code Change Relevance Journal Article
In: International Journal of Software Engineering and Knowledge Engineering, 26 (05), pp. 733–768, 2016.
@article{haraty2016regression,
title = {Regression Test Cases Prioritization Using Clustering and Code Change Relevance},
author = {Ramzi A Haraty and Nashat Mansour and Lama Moukahal and Iman Khalil},
url = {https://www.worldscientific.com/doi/abs/10.1142/S0218194016500248},
doi = {10.1142/S0218194016500248},
year = {2016},
date = {2016-01-01},
urldate = {2016-01-01},
journal = {International Journal of Software Engineering and Knowledge Engineering},
volume = {26},
number = {05},
pages = {733--768},
publisher = {World Scientific},
abstract = {Regression testing is important for maintaining software quality. However, the cost of regression testing is relatively high. Test case prioritization is one way to reduce this cost. Test case prioritization techniques sort test cases for regression testing based on their importance. In this paper, we design and implement a test case prioritization method based on the location of a change. The method consists of three steps: (1) clustering test cases, (2) prioritizing the clusters with respect to the relevance of the clusters to a code change, and (3) test case prioritization within each cluster based on metrics. We propose a metric for measuring test case importance based on Requirement Complexity, Code Complexity, and Code Coverage. To evaluate our method, we apply it on a launch interceptor problem program, and measure the inclusiveness and precision for clusters of test cases with respect to code change in specific test cases. Our results show that our proposed change-based prioritization method increases the likelihood of executing more relevant test cases earlier.},
keywords = {},
pubstate = {published},
tppubtype = {article}
}
Regression testing is important for maintaining software quality. However, the cost of regression testing is relatively high. Test case prioritization is one way to reduce this cost. Test case prioritization techniques sort test cases for regression testing based on their importance. In this paper, we design and implement a test case prioritization method based on the location of a change. The method consists of three steps: (1) clustering test cases, (2) prioritizing the clusters with respect to the relevance of the clusters to a code change, and (3) test case prioritization within each cluster based on metrics. We propose a metric for measuring test case importance based on Requirement Complexity, Code Complexity, and Code Coverage. To evaluate our method, we apply it on a launch interceptor problem program, and measure the inclusiveness and precision for clusters of test cases with respect to code change in specific test cases. Our results show that our proposed change-based prioritization method increases the likelihood of executing more relevant test cases earlier.