Nov 2026· Proceedings of the 2026 8th Joint Workshop on CPS&IoT Security and Privacy· 0 citations· 10 references
Abstract
Robotic vehicles, such as Unmanned Aerial Vehicles (UAVs), are deployed in safety-critical applications ranging from package delivery to search and rescue operations. In these cyber-physical systems, software vulnerabilities can cause physical consequences such as collisions and mission failures, giving them direct safety implications. Most existing security research has focused on core control software. However, peripheral subsystems such as proximity sensors, optical flow sensors, and camera gimbals remain under-tested despite directly influencing control decisions, creating opportunities for attackers to manipulate vehicle behavior without immediately triggering software-level alarms. In this paper, we present DroneFuzz, a fuzzing framework for discovering cyber-physical vulnerabilities (CPVs) in robotic vehicle peripheral subsystems. DroneFuzz targets MAVLink-based systems and uses a grammar-based mutation engine to generate semantically valid peripheral inputs. The engine parses publicly available MAVLink XML specifications to produce well-formed messages, allowing us to explore peripheral-dependent code paths. DroneFuzz addresses the challenge of separating genuine safety violations from normal flight variations caused by wind, turbulence, and sensor noise using a novel hybrid bug oracle that combines Dynamic Time Warping (DTW) with Long Short-Term Memory (LSTM) autoencoders. We evaluate DroneFuzz on ArduPilot and PX4, two widely used autopilot systems. DroneFuzz reproduces five known vulnerabilities and discovers two previously unknown bugs in proximity sensor and optical flow subsystems. To support reproducibility, we release our implementation of the framework and configuration artifacts. These findings indicate that peripheral subsystems are a practical and largely overlooked attack surface.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.