Drone security has two sides: protecting aircraft and data from interference or unauthorized access, and protecting people or sites from unwanted drone activity. This section covers command links, software and firmware security, access control, spoofing and jamming risks, data protection, detection, counter-UAS concepts, and the limits that legal and technical constraints place on defensive measures.
Topic
Drone Security: Cybersecurity, Counter-UAS and System Protection
Latest topic news
ArduPilot AP_Periph reviews off-by-one tunnel serial-port validation
ArduPilot PR 35064 changes a port check that rejected serial IDs only above an array's element count; a value equal to the count could pass and index beyond the final valid entry.
Read newsBetaflight VTX table command proposal closes a frequency-array write boundary
Betaflight PR 15989 describes an optional FACTORY or CUSTOM flag in vtxtable band parsing that leaves the channel index at -1 when writing frequencies. The proposed fix advances the parser correctly.
Read newsBetaflight CLI parser fixes target negative channel and range indexes
Betaflight PR 15988 says the aux, adjrange and vtx CLI commands previously checked upper bounds but not negative values returned by atoi(), allowing indexes such as -1 to select memory before an array. It proposes lower-bound validation.
Read newsBetaflight firmware-image packing change adds explicit S-record validation
Betaflight PR 15983 proposes preserving S-record header information, zero addresses and the final data region while packing DfuSe images, and validating record byte counts and checksums before output.
Read newsPX4 ST24 parser review finds a shared RC buffer index risk
PX4 PR 29693 reports that protocol auto-scanning can rotate among decoder types without resetting an ST24 decoder's partial state, leaving a possible write index beyond the shared rc decode buf union. The proposal adds bounds checks.
Read newsTopic articles
A camera model name should not decide where a ground station writes files
An onboard camera needs a name so that a ground-control application can show its settings. It should not get to choose a directory on the operator's computer.
Read articleA drone's Remote ID signal cannot prove its flight is authorized
A receiver can decode a drone's identifier, position and broadcast status without learning whether that aircraft has permission to fly where it is. That distinction is easy to lose when a single map combines radio detections, planned flights and airspace rules. The symbols may look similar; the evidence behind them is not.
Read article