-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathpublications.bib
More file actions
4753 lines (4513 loc) · 277 KB
/
Copy pathpublications.bib
File metadata and controls
4753 lines (4513 loc) · 277 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
@Thesis{ volpatto_thesis_2010,
Author = {Volpatto, Alberto},
Title = {Negoziazione cooperativa e meccanismi adattativi per
mitigare gli attacchi contro le applicazioni web},
Year = {2010},
Institution = {Politecnico di Milano}
}
@Thesis{ visentin_thesis_2010,
Author = {Visentin, Luca and Todisco, Stefano},
Title = {Pcapstat: un sistema per supportare l’analisi del traffico
di rete},
Year = 2010,
Institution = {Politecnico di Milano}
}
@Thesis{ testa_thesis_2007,
Author = {Testa, Pietro},
Title = {Valutazione automatica delle performance di sistemi di
anomaly detection},
Year = 2007,
Institution = {Politecnico di Milano}
}
@Thesis{ rizzi_thesis_2010,
Author = {Rizzi, Alessandro and Schiavoni, Stefano},
Title = {WebLorica: Un framework per lo sviluppo di anomaly detection
system per applicazioni web},
Year = 2010,
Institution = {Politecnico di Milano}
}
@Article{ pogliani_article_2019,
Author = {Pogliani, Marcello and Quarta, Davide and Polino, Mario and
Vittone, Martino and Maggi, Federico and Zanero, Stefano},
Title = {Security of controlled manufacturing systems in the
connected factory: the case of industrial robots},
Journal = {Journal of Computer Virology and Hacking Techniques},
Abstract = {In modern factories, ``controlled'' manufacturing systems,
such as industrial robots, CNC machines, or 3D printers, are
often connected in a control network, together with a
plethora of heterogeneous control devices. Despite the
obvious advantages in terms of production and ease of
maintenance, this trend raises non-trivial cybersecurity
concerns. Often, the devices employed are not designed for an
interconnected world, but cannot be promptly replaced: In
fact, they have essentially become legacy systems, embodying
design patterns where components and networks are accounted
as trusted elements. In this paper, we take a holistic view
of the security issues (and challenges) that arise in
designing and securely deploying controlled manufacturing
systems, using industrial robots as a case study---indeed,
robots are the most representative instance of a complex
automatically controlled industrial device. Following up to
our previous experimental analysis, we take a broad look at
the deployment of industrial robots in a typical factory
network and at the security challenges that arise from the
interaction between operators and machines; then, we propose
actionable points to secure industrial cyber-physical
systems, and we discuss the limitations of the current
standards in industrial robotics to account for active
attackers.},
DOI = {10.1007/s11416-019-00329-8},
ISSN = {2263-8733},
Year = {2019},
Month = {Feb},
day = {13},
File = {files/papers/journal-papers/pogliani_article_2019.pdf}
}
@Thesis{ peri_thesis_2010,
Author = {Peri, Lorenzo},
Title = {Metodi K-nearest-neighbor per la rilevazione automatica di
attacchi informatici},
Year = 2010,
Institution = {Politecnico di Milano}
}
@Thesis{ michelini_thesis_2008,
Author = {Michelini, Matteo},
Title = {Kernel auditing su Linux 2.6 in formato OpenBSM},
Year = 2008,
Institution = {Politecnico di Milano}
}
@Thesis{ magni_thesis_2007,
Author = {Magni, Claudio},
Title = {Analisi e test automatizzati di sistemi di anomaly detection
network-based},
Year = 2007,
Institution = {Politecnico di Milano}
}
@Thesis{ lever_thesis_2010,
Author = {Lever, Eros},
Title = {Un sistema di raccolta dati per lo studio delle minacce
celate dagli URL brevi},
Year = 2010,
Institution = {Politecnico di Milano}
}
@Thesis{ lancini_thesis_2010,
Author = {Lancini, Marco},
Title = {FacePrivacy},
Year = 2010,
Institution = {Politecnico di Milano}
}
@Thesis{ gressi_thesis_2009,
Author = {Gressi, Erika},
Title = {Apprendimento e simulazione dell’attività di un utente
mediante l’utilizzo di modelli semi- markoviani nascosti},
Year = 2009,
Institution = {Politecnico di Milano}
}
@Thesis{ debiasi_thesis_2007,
Author = {Debiasi, Matteo and Falsitta, Matteo},
Title = {Reingengerizzazione ed ottimizzazione di un sistema di
anomaly detection host based},
Year = 2007,
Institution = {Politecnico di Milano}
}
@Thesis{ clerici_thesis_2010,
Author = {Clerici, Marco and Sasso, Mattia},
Title = {Analisi Sperimentale delle vulnerabilità di Google
reCAPTCHA},
Year = 2010,
Institution = {Politecnico di Milano}
}
@Thesis{ benefico_thesis_2010,
Author = {Benefico, Simone and Colombo, Andrea},
Title = {Reingegnerizzazione di un riconoscitore automatico di
attacchi di rete},
Year = 2010,
Institution = {Politecnico di Milano}
}
@Unpublished{ yen_ddsbheu_talk_2021,
ShortTitle = {DDSBHEU},
Author = {Yen, Ta-Lun and Maggi, Federico and Boasson, Erik},
Title = {The Data Distribution Service (DDS) Protocol is Critical:
Let's Use it Securely!},
EventTitle = {Black Hat Briefings Europe},
Abstract = {We discovered and disclosed vulnerabilities in most of the
OMG Data Distribution Service (DDS) implementations. DDS
enables crucial technologies like autonomous driving,
healthcare machinery, military tactical systems, or missile
launch stations. Notably, DDS is used by NASA at the KSC, by
SIEMENS for smart grid applications, by Volkswagen and Bosch
for autonomous valet parking systems, by NAV CANADA for ATC,
and by the Robot Operating System 2 (ROS2) to control
industrial and consumer robots.
Designed around industrial-level requirements, DDS sits deep
in the control network, allowing an arbitrary number of
endpoints like sensors or actuators to communicate
transparently, with an abstract API based on familiar data
type specifications (e.g., C structs) and simple function
calls, regardless of the complexity of the data.
We approached DDS from the bottom up, and we will show you
how we wrote a Scapy layer to guide you through the packet
structure. Although network fuzzing wasn't directly
effective, it greatly helped us to master the tiny details of
DDS. This led us to find an amplification vulnerability in
the standard, which allows an attacker to redirect flood an
arbitrary host. DDS configuration is highly dependent on XML,
JSON, YAML, or similar formats, which make them another
attack vector. By writing a Radamsa-based file fuzzer we
found a parsing vulnerability in RTI DDS Connector, so an
attacker can use a malicious configuration file to gain
initial access. We then focus on fuzzing the message
interpretation routines in all implementations. Using
concrete examples, we explain how to pick good fuzz targets
and prepare them for popular frameworks like OSS-Fuzz and
UnicornAFL.
We take you from knowing nothing about DDS to efficiently
researching new vulnerabilities, which we encourage other
researchers, DDS users and implementors to do. We report on
our interactions with some of the DDS implementors, which we
believe is the first concrete step towards securing this
critical protocol in the long run. We release fuzzing
harnesses and a Scapy layer to decode the DDS RTPS layer.},
Location = {London, UK},
URL = {https://www.blackhat.com/eu-21/briefings/schedule/index.html#the-data-distribution-service-dds-protocol-is-critical-lets-use-it-securely-24934},
Date = {2021-11-08},
HowPublished = {Peer-reviewed Talk},
File = {files/talks/yen_ddsbheu_talk_2021.pdf}
}
@Unpublished{ mayoral-vilches_smallwonderbhus_talk_2021,
ShortTitle = {SmallWonderBHUS},
Author = {Mayoral-Vilches, Víctor and Maggi, Federico},
Title = {Small Wonder: Uncovering Planned Obsolescence Practices in
Robotics and What This Means for Cybersecurity},
EventTitle = {Black Hat Briefings USA},
Abstract = {Security in robotics is nothing really new if one considers
modern OT and IT approaches, and most security practices
translate directly to robots. However, there's almost no
security culture amongst robot makers.
Building a robot requires careful selection of components
that interact across networks while meeting timing deadlines.
It isn't uncommon for robot components to be compromised or
fail over time, leading to complete system malfunction. Given
the expensive prices of these machines (we focus on robots in
the 25K-70K USD range), it's only reasonable to consider the
need for securing and repairing robots.
We introduce and promote systematic "robot teardown" as an
approach to repair robots by understanding their internals
(still obscure). Needless to say, robot teardown is an
essential practice in robot security. We show several "tricks
from the trade" and the legal implications learned by porting
reverse-engineering practices into the less-explored field of
robotics. We explain how we a) discovered more than 90
security vulnerabilities in robots from Teradyne (MiR and UR)
over a period of two years (never discussed publicly before),
b) gained repairing capabilities on these robots, c) show
evidence of planned obsolescence by comparing two
sequentially released robot controllers, and d) demonstrate
how robot hacking leads us to repurpose an older controller
(previous version) from Universal Robots with their newer
robots (arms) maintaining full capabilities and demonstrating
that there's no need to re-spend thousands of dollars again.
Similar to Ford in the 1920s with cars, most robot
manufacturers nowadays employ planned obsolescence practices
and organize dealers and system integrators into "private
networks", providing repair parts only to "certified"
companies to make repairs more difficult and evade
competition. We wrap up by advocating for a "Right to
Repair'' in robotics to reduce robot e-waste and promote
systematic teardowns for the benefit of security research.},
Location = {Las Vegas, US},
URL = {https://www.blackhat.com/us-20/briefings/schedule/index.html#otrazor-static-code-analysis-for-vulnerability-discovery-in-industrial-automation-scripts-19523},
Date = {2021-07-31},
HowPublished = {Peer-reviewed Talk},
File = {files/talks/mayoral-vilches_smallwonderbhus_talk_2021.pdf}
}
@TechReport{ maggi_rfquack_tr_2021,
ShortTitle = {RFQuack},
Author = {Maggi, Federico and Guglielmini, Andrea},
Title = {RFQuack: A Universal Hardware-Software Toolkit for Wireless
Protocol (Security) Analysis and Research},
Institution = {arXiv},
Abstract = {Software-defined radios (SDRs) are indispensable for signal
reconnaissance and physical-layer dissection, but despite we
have advanced tools like Universal Radio Hacker, SDR-based
approaches require substantial effort. Contrarily, RF dongles
such as the popular Yard Stick One are easy to use and
guarantee a deterministic physical-layer implementation.
However, they're not very flexible, as each dongle is a
static hardware system with a monolithic firmware. We present
RFquack, an open-source tool and library firmware that
combines the flexibility of a software-based approach with
the determinism and performance of embedded RF frontends.
RFquack is based on a multi-radio hardware system with
swappable RF frontends, and a firmware that exposes a
uniform, hardware-agnostic API. RFquack focuses on a
structured firmware architecture that allows high- and
low-level interaction with the RF frontends. It facilitates
the development of host-side scripts and firmware plug-ins,
to implement efficient data-processing pipelines or
interactive protocols, thanks to the multi-radio support.
RFquack has an IPython shell and 9 firmware modules for:
spectrum scanning, automatic carrier detection and bitrate
estimation, headless operation with remote management,
in-flight packet filtering and manipulation, MouseJack, and
RollJam (as examples). We used RFquack to setup RF hacking
contests, analyze industrial-grade devices and key fobs, on
which we found and reported 11 vulnerabilities in their RF
protocols. },
Date = {2021-04-06},
URL = {https://arxiv.org/abs/2104.02551},
File = {files/papers/reports/maggi_rfquack_tr_2021.pdf}
}
@InProceedings{ maggi_smsec_2020,
ShortTitle = {SMSec},
Author = {Maggi, Federico and Balduzzi, Marco and Vosseler, Rainer and
Rösler, Martin and Quadrini, Walter and Tavola, Giacomo and
Pogliani, Marcello and Quarta, Davide and Zanero, Stefano},
Title = {Smart Factory Security: A Case Study on a Modular
SmartManufacturing System},
Publisher = {Elsevier Procedia Computer Science},
BookTitle = {International Conference on Industry 4.0 and Smart
Manufacturing},
Volume = {42},
Series = {ISM '20},
Location = {Linz, Austria},
Abstract = {Smart manufacturing systems are an attractive target for
cyber attacks, because they embed valuable data andcritical
equipment. Despite the market is driving towards integrated
and interconnected factories, current smartmanufacturing
systems are still designed under the assumption that they
will stay isolated from the corporatenetwork and the outside
world. This choice may result in an internal architecture
with insufficient network andsystem compartmentalization. As
a result, once an attacker has gained access, they have full
control of the entireproduction plant because of the lack of
network segmentation.With the goal of raising cybersecurity
awareness, in this paper we describe a practical case study
showing attackscenarios that we have validated on a real
modular smart manufacturing system, and suggest practical
securitycountermeasures. The testbed smart manufacturing
system is part of the Industry 4.0 research laboratory hosted
byPolitecnico di Milano, and comprises seven assembly
stations, each with their programmable logic controllers
andhuman-computer interfaces, as well as an industrial
robotic arm that performs pick-and-place tasks.On this
testbed we show two indirect attacks to gain initial access,
even under the best-case scenario of a system notdirectly
connected to any public network. We conclude by showing two
post-exploitation scenarios that an adversarycan use to cause
physical impact on the production, or keep persistent access
to the plant.We are unaware of a similar security analysis
performed within the premises of a research facility,
following ascientific methodology, so we believe that this
work can represent a good first step to inspire follow up
research onthe many verticals that we touch.},
Date = {2020-11-23},
File = {files/papers/conference-papers/maggi_smsec_2020.pdf}
}
@InProceedings{ pogliani_otrazor_2020,
ShortTitle = {OTRazor},
Author = {Pogliani, Marcello and Maggi, Federico and Balduzzi, Marco
and Quarta, Davide and Zanero, Stefano},
Title = {Detecting Unsafe Code Patterns in Industrial Robot
Programs},
Publisher = {ACM},
BookTitle = {Proceedings of the 15th ACM Asia Conference on Computer and
Communications SecurityOctober 2020},
Series = {AsiaCCS '20},
Pages = {759--771},
Address = {New York, NY, USA},
Location = {Taipei, Taiwan},
Abstract = {In this paper, we analyze the languages of $8$ leading
industrial robot vendors, systematize their technical
features, and discuss cases of vulnerable and malicious uses.
We then describe a static source-code analyzer that we
created to analyze robotic programs and discover insecure or
potentially malicious code paths. We focused our
proof-of-concept implementation on two popular languages,
namely ABB's RAPID and KUKA's KRL. By evaluating our tool on
a set of publicly available programs, we show that insecure
patterns are found in real-world code; therefore, static
source-code analysis is an effective security screening
mechanism, for example to prevent commissioning insecure or
malicious industrial task programs. Finally, we discuss
remediation steps that developers and vendors can adopt to
mitigate such issues.},
DOI = {https://doi.org/10.1145/3320269.3384735},
Date = {2020-10-5},
File = {files/papers/conference-papers/pogliani_otrazor_2020.pdf}
}
@Unpublished{ maggi_smscs3sthlm_talk_2020,
ShortTitle = {SMSCS3STHLM},
Author = {Maggi, Federico},
Title = {Hidden Attack Surfaces of Modern Industrial Automation
Systems},
EventTitle = {CS3STHLM},
Abstract = {Last year we performed a security analysis on a testbed
smart manufacturing system using a variety of
"unconventional" attack vectors. Striving to think very much
outside the box, we wanted to understand which overlooked
conditions and attacker capabilities make certain attacks
possible, and their consequences.
Through concrete PoCs, we'll describe what unconventional
attack vectors and very creative attackers can achieve, as
well as how they can be stopped by current security
solutions.
We'll first show how a remote attacker can indirectly
compromise an engineering workstation to backdoor the
automation logic of an industrial robot. Then, we'll reveal
how the attack has been carried out via a malicious software
extension that targets the simulation and offline programming
(OLP) platform. The attendees will learn that such malicious
extensions have full capabilities on the target system, but
we'll explain what they are and how they can be stopped.
Our second entry point is an industry-grade embedded device.
These devices, often dubbed as "IIoT devices" offer great
programming flexibility—compared to, say, PLCs—at the
price of more responsibility for the programmers. The
proliferation of customizable IIoT devices along with the
many 3rd-party development libraries are the perfect target
for software supply-chain attacks. We'll show how we
trojanized a simple temperature-measurement library to
implement an ARP-based DoS attack, along with inaccurate
temperature data-points, which can cause cascade effects down
the data-processing pipeline. We'll argue that detecting
violations in the software supply-chain is hard in large,
distributed enterprises, but their effects can be mitigated
with proper network partitioning.
The last step of our security analysis focused on lateral
movements to complex, programmable machines such as
industrial robots. We observe that, movement-instructions
aside, industrial robot programming languages have
statements, loops, conditions, network sockets, serial
communication, etc. With access to low-level system resources
like files, network, memory, and peripherals, task programs
are a powerful, overlooked payload. Not only we show that
task programs are susceptible to input-validation
vulnerabilities, we also show that they're rich enough to
implement malware-like functionalities, given that the
runtime environment provides no resource isolation. As a
result, task programs have unmediated access to the entire
system.
We'll share cases of vulnerable and malicious task programs,
and how to discover such patterns, including some
vulnerabilities we found in real-world code.
We conclude by discussing the remediation steps that can be
adopted by developers and vendors to mitigate our findings in
the medium and long term.},
Location = {Stocholm, Sweden},
URL = {https://cs3sthlm.se/agenda/},
Date = {2020-10-21},
HowPublished = {Peer-reviewed Talk},
File = {files/talks/maggi_smscs3sthlm_talk_2020.pdf}
}
@Unpublished{ maggi_otrazorhitcon_talk_2020,
ShortTitle = {OTRazorHITCON},
Author = {Maggi, Federico and Pogliani, Marcello and Quarta, Davide
and Zanero, Stefano and Balduzzi, Marco},
Title = {Guarding the Factory Floor: Catching Insecure Industrial
Robot Programs},
EventTitle = {HITCON},
Abstract = {What if a perfectly patched industrial manufacturing machine
can still harbor for vulnerabilities where no one is looking?
What if the powerful programming languages used to program
these machines can go beyond simple movement instructions,
and actually allow threat actors to hide malware into the
logic?
Industrial robot OEMs provide proprietary, legacy programming
languages to automate these complex machines. Mostly offering
movement primitives, theseprogramming languages also give
access to low-level system resources like files, network
sockets, and some even allow memory and program pointer.
While useful, these features may lead to insecure programming
patterns such as input-validation vulnerabilities. Also,
they’re powerful enough to allow the implementation of
advanced malware functionalities, with an underlying runtime
environment that provides no resource isolation.
After going through the technical features of the languages
by eight leading OEMs, we'll share cases of vulnerable and
malicious usage. We'll then present a static code analyzer
that we created and patented, to scan robotic programs and
discover unsafe code patterns. Our evaluation on 100
automation task program files show that insecure patterns are
indeed found in real-world code, and that static source code
analysis is an effective defense tool in the short term.},
Location = {Taiwan},
URL = {https://hitcon.org/2020/agenda/93ba0758-bd84-43ae-9da0-b389fde2803b/},
Date = {2020-09-12},
HowPublished = {Peer-reviewed Talk},
File = {files/talks/maggi_otrazorhitcon_talk_2020.pdf}
}
@Unpublished{ maggi_otrazorbhus_talk_2020,
ShortTitle = {OTRazorBHUS},
Author = {Maggi, Federico and Pogliani, Marcello and Quarta, Davide
and Zanero, Stefano and Balduzzi, Marco},
Title = {OTRazor: Static Code Analysis for Vulnerability Discovery in
Industrial Automation Scripts},
EventTitle = {Black Hat Briefings USA},
Abstract = {In this talk, we delve into industrial robot programming,
focusing on the security issues arising from the design and
implementation choices of these platforms.
Industrial robot manufacturers provide proprietary,
domain-specific programming languages to operate these
complex machines. Mostly focused on movement instructions,
such programming languages also provide access to low-level
system resources like files and network access, and some even
allow dynamic code loading. While useful, these features can
lead to unsafe programming patterns such as input-validation
vulnerabilities or malware-like functionalities, especially
if the underlying environment provides no resource isolation
like those found in modern operating systems.
After describing the technical features of the languages by
eight leading manufacturers, we'll share several cases of
vulnerable and malicious usage. We'll then present a static
code analyzer that we created and patented, to scan robotic
programs and discover unsafe code patterns. Our evaluation on
50 automation programs show that unsafe patterns are indeed
found in real-world code, and that static source code
analysis is an effective defense tool in the short term.
We conclude by discussing the remediation steps that can be
adopted by developers and vendors to mitigate such issues in
the medium and long term.},
Location = {Las Vegas, US},
URL = {https://www.blackhat.com/us-20/briefings/schedule/index.html#otrazor-static-code-analysis-for-vulnerability-discovery-in-industrial-automation-scripts-19523},
Date = {2020-08-05},
HowPublished = {Peer-reviewed Talk},
File = {files/talks/maggi_otrazorbhus_talk_2020.pdf}
}
@TechReport{ maggi_rogueautomationwp_tr_2020,
ShortTitle = {RogueAutomationWP},
Author = {Maggi, Federico and Pogliani, Marcello and Vittone, Martino,
and Quarta, Davide and Zanero, Stefano and Balduzzi, Marco
and Vosseler, Rainer and Rösler, Martin},
Title = {Rogue Automation: Vulnerable and Malicious Code in
Industrial Programming},
Institution = {Trend Micro, Inc.},
Abstract = {In this research paper, we reveal previously unknown design
flaws that malicious actors could exploit to hide malicious
functionalities in industrial robots and other automated,
programmable manufacturing machines. Since these flaws are
difficult to fix, enterprises that deploy vulnerable machines
could face serious consequences. An attacker could exploit
them to become persistent within a smart factory, silently
alter the quality of products, halt a manufacturing line, or
perform some other malicious activity.},
Date = {2020-08-04},
URL = {https://www.trendmicro.com/vinfo/us/security/news/internet-of-things/unveiling-the-hidden-risks-of-industrial-automation-programming},
Series = {Research Papers},
Publisher = {Trend Micro Research},
File = {files/papers/reports/maggi_rogueautomationwp_tr_2020.pdf}
}
@TechReport{ maggi_smartfactorywp_tr_2020,
ShortTitle = {SmartFactoryWP},
Author = {Maggi, Federico and Pogliani, Marcello},
Title = {Attacks on Smart Manufactururing Systems: A Forward-looking
Security Analysis},
Institution = {Trend Micro, Inc.},
Abstract = {This research presents a systematic security analysis that
we performed to explore a variety of attack vectors on a real
smart manufacturing system and to assess the attacks that
could be feasibly launched on a complex smart manufacturing
system. The main, two-pronged question we want to answer is:
Under which threat conditions and attacker capabilities are
certain attacks possible, and what are the consequences?},
Date = {2020-05-11},
URL = {https://www.trendmicro.com/vinfo/us/security/news/internet-of-things/threats-and-consequences-a-security-analysis-of-smart-manufacturing-systems},
Series = {Research Papers},
Publisher = {Trend Micro Research},
File = {files/papers/reports/maggi_smartfactorywp_tr_2020.pdf}
}
@TechReport{ hilt_factoryhoneypotwp_tr_2020,
ShortTitle = {FactoryHoneypotWP},
Author = {Hilt, Stephen and Maggi, Federico and Perine, Charles and
Remorin, Lord and Rösler, Martin and Vosseler, Rainer},
Title = {Caught in the Act: Running a Realistic Factory Honeypot to
Capture Real Threats},
Institution = {Trend Micro, Inc.},
Abstract = {Different critical infrastructures have been hit with
attacks such as those that involved the infamous Stuxnet
malware1 and the more recent Triton malware. These incidents
— attacks on manufacturing and other sectors that use
industrial control systems (ICSs) — continue to be heard of
through the years. In 2017, for instance, the notorious
WannaCry ransomware shut down a car manufacturing factory in
Japan, and another ransomware attack took down a factory in
North Carolina, U.S. Smart factories attract the interest of
threat actors for the critical and sensitive infrastructures
they usually handle. A successful attack, no matter how
difficult the execution, can yield high-impact results that
can corner an organization into giving in to
cybercriminals’ demands or, at the very least, cost it
considerable losses.Prompted by our desire to determine how
knowledgeable and imaginative attackers could be in
compromising a manufacturing facility, we built the most
realistic factory honeypot we had ever created. And in doing
so, we also created an ideal environment where we could
monitor and learn about the attacks that the honeypot came to
attract. From conceptualization to actual execution, our
factory honeypot was designed to be an attractive target for
potential cybercriminals.Our factory honeypot took on the
ruse of a small fictitious company that apparently handled
clients from critical industries yet possessed inadequate
security defenses. Our ruse proved successful as our honeypot
saw several attacks, which we had the freedom and resources
to monitor. These attacks included a malicious cryptocurrency
mining campaign, two ransomware attacks, another that posed
as a ransomware attack, and several scanners.In this research
paper, we detail the conceptualization and creation of our
most elaborate honeypot to date, and discuss the result of
our monitoring and tracking of the incidents that occurred on
the honeypot.},
Date = {2020-01-21},
URL = {https://www.trendmicro.com/vinfo/us/security/news/internet-of-things/fake-company-real-threats-logs-from-a-smart-factory-honeypot},
Series = {Research Papers},
Publisher = {Trend Micro Research},
File = {files/papers/reports/hilt_factoryhoneypotwp_tr_2020.pdf}
}
@InProceedings{ maggi_industrialradios_2019,
ShortTitle = {IndustrialRadios},
Author = {Maggi, Federico and Balduzzi, Marco and Andersson, Jonathan
and Lin, Philippe and Hilt, Stephen and Urano, Akira and
Vosseler, Rainer},
Title = {A Security Evaluation of Industrial Radio Remote
Controllers},
Publisher = {Springer International Publishing},
Editor = {Perdisci, Roberto and Almgren, Magnus},
BookTitle = {Proceedings of the 16th International Conference on
Detection of Intrusions and Malware, and Vulnerability
Assessment (DIMVA)},
Volume = {11543},
Pages = {(to appear)},
Location = {Gothenburg, Sweden},
Abstract = {Heavy industrial machinery is a primary asset for the
operation of key sectors such as construction, manufacturing,
and logistics. Targeted attacks against these assets could
result in incidents, fatal injuries, and substantial
financial loss. Given the importance of such scenarios, we
analyzed and evaluated the security implications of the
technology used to operate and control this machinery, namely
industrial radio remote controllers. We conducted the
first-ever security analysis of this technology, which relies
on proprietary radio-frequency protocols to implement
remote-control functionalities. Through a two-phase
evaluation approach we discovered important flaws in the
design and implementation of industrial remote controllers.
In this paper we introduce and describe 5 practical attacks
affecting major vendors and multiple real-world
installations. We conclude by discussing how a challenging
responsible disclosure process resulted in first-ever
security patches and improved security awareness.},
DOI = {10.1007/978-3-030-22038-9_7},
ISBN = {978-3-030-22037-2},
Date = {2019-06-19},
File = {files/papers/conference-papers/maggi_industrialradios_2019.pdf}
}
@Unpublished{ balduzzi_industrialradioshitb_talk_2019,
ShortTitle = {IndustrialRadiosHITB},
Author = {Balduzzi, Marco and Maggi, Federico},
Title = {Hey Operator, Where’s Your Crane? Attacking Industrial
Remote Controllers},
EventTitle = {Hack In The Box Amsterdam},
Abstract = {Radio-frequency (RF) remote controllers are widely used in
multiple industrial applications like manufacturing,
construction and transportation. Cranes, drillers and
diggers, among others, are commonly equipped with RF
controllers, which have become the weakest link in
safety-critical IIoT applications.
Our security assessment revealed a lack of important security
features at different levels, with vendors using obscure
proprietary protocols instead of standards. As a consequence,
this technology appeared to be vulnerable to attacks like
replay, command injection, e-stop abuse, malicious repairing
and reprogramming. Together with ZDI, we ran into a 6-months
responsible disclosure process and then released 10 security
advisories.
In this presentation, we share the findings of our research
and make use of demos to discuss the problems in detail. We
conclude providing recommendations for all parties involved
in the life-cycle of these devices, from vendors to users and
system integrators.},
Location = {Amsterdam, The Netherlands},
URL = {https://conference.hitb.org/hitbsecconf2019ams/sessions/hey-operator-wheres-your-crane-attacking-industrial-remote-controllers/},
Date = {2019-05-10},
HowPublished = {Peer-reviewed Talk},
File = {files/talks/balduzzi_industrialradioshitb_talk_2019.pdf}
}
@Unpublished{ maggi_rfquack_talk_2019,
ShortTitle = {RFQuack},
Author = {Maggi, Federico},
Title = {RFQuack: The RF-Analysis Tool That Quacks},
EventTitle = {HITB Amsterdam},
Abstract = {RFQuack is the versatile RF-analysis tool that quacks! It's
a library firmware that allows you to sniff, manipulate, and
transmit data over the air. And if you're not happy how the
default firmware functionalities, we made it easy to extend.
Consider it as the hardware-modular and developer-friendly
version of the great YardStick One, which is based on the
CC1111 radio chip. Differently from that and other RF
dongles, RFQuack is designed to be agnostic with respect to
the radio chip. So if you want to use, say, the RF69, you can
do it. If you need to use the CC110L or CC1120, you can do
it. Similarly to RFCat, RFQuack has console based, Python
scriptable, client that allows you to set parameters,
receive, transmit, and so on.},
Location = {Amsterdam, The Netherlands},
URL = {https://github.com/trendmicro/RFQuack},
Date = {2019-05-09},
HowPublished = {Peer-reviewed Demo},
File = {files/talks/maggi_rfquack_talk_2019.pdf}
}
@Unpublished{ maggi_m2mhmi_talk_2019,
ShortTitle = {M2MHMI},
Author = {Maggi, Federico},
Title = {Machine-to-Machine Protocol Security: The Case of MQTT and
CoAP},
EventTitle = {Hannover Messe},
Abstract = {MQTT and CoAP provide data connectivity for practically any
kind of "machines". This talk will cover the results of our
security analysis of MQTT and CoAP, which uncovered issues in
the design specifications, vulnerable product
implementations, and hundreds of thousands unsecured,
open-to-the-world deployments. Despite the fixes in the
design specifications, it is hard for developers to keep up
with a changing standard when a technology becomes pervasive.
Also, the market of this technology is very wide because the
barrier to entry is fairly low. This led to a multitude of
fragmented implementations. Our findings have been
acknowledged by the vendors, by the MQTT Technical Committee,
which released a note to help identify the risks, and
received the attention of several other organizations. Using
MQTT and CoAP as case study, we will provide recommendations
at various levels, in the hope to see a significant reduction
in the number of insecure deployments in the future.},
Location = {Hannover, Germany},
Date = {2019-04-04},
HowPublished = {Selected Talk},
URL = {https://www.hannovermesse.de/event/machine-to-machine-protocol-security-the-case-of-mqtt-and-coap/VOR/90582},
File = {files/talks/maggi_m2mhmi_talk_2019.pdf}
}
@TechReport{ andersson_industrialradioswp_tr_2019,
ShortTitle = {IndustrialRadiosWP},
Author = {Andersson, Jonathan and Balduzzi, Marco and Hilt, Stephen
and Lin, Philippe and Maggi, Federico and Urano, Akira and
Vosseler, Rainer},
Title = {A Security Analysis of Radio Remote Controllers for
Industrial Applications},
Institution = {Trend Micro, Inc.},
Abstract = {Radio frequency (RF) remote controllers are widely used in
manufacturing, construction, transportation, and many other
industrial applications. Cranes, drills, and miners, among
others, are commonly equipped with RF remotes. Unfortunately,
these devices have become the weakest link in these
safety-critical applications, characterized by long life
spans, high replacement costs, and cumbersome patching
processes. Given the pervasive connectivity promoted by the
Industry 4.0 trend, we foresee a security risk in this domain
as has happened in other fields.
Our research reveals that RF remote controllers are
distributed globally, and millions of vulnerable units are
installed on heavy industrial machinery and environments. Our
extensive in-lab and on-site analysis of devices made by
seven popular vendors reveals a lack of security features at
different levels, with obscure, proprietary protocols instead
of standard ones. They are vulnerable to command spoofing, so
an attacker can selectively alter their behavior by crafting
arbitrary commands — with consequences ranging from theft
and extortion to sabotage and injury.
This research analyzes and shows how an attacker can
persistently and remotely take control or simulate the
malfunction of the attached machinery, through attacks like
command injection, emergency-stop (e-stop) abuse, and
malicious re-pairing. In addition, many modern radio
controllers can be programmed via software, which also lacks
any security measures, opening them to remote attack vectors.
A remote attacker who compromises the computer used to
program these remotes can alter their firmware to implement
persistent and sophisticated attacks.
Having examined the root cause of the vulnerabilities that
make these attacks possible, we have reached out to the
affected vendors to promote suitable mitigation, and we hope
that our research will help raise awareness and avoid
unfortunate situations regarding RF remote controllers in
industrial applications.},
Date = {2019-01-15},
URL = {https://documents.trendmicro.com/assets/white_papers/wp-a-security-analysis-of-radio-remote-controllers.pdf},
Series = {Research Papers},
Publisher = {Trend Micro Research},
File = {files/papers/reports/andersson_industrialradioswp_tr_2019.pdf}
}
@Unpublished{ maggi_mqttbheu_talk_2018,
ShortTitle = {MQTTBHEU},
Author = {Maggi, Federico and Quarta, Davide},
Title = {When Machines Can't Talk: Security and Privacy Issues of
Machine-to-Machine Data Protocols},
EventTitle = {Black Hat Briefings Europe},
Abstract = {Two popular machine-to-machine (M2M) protocols—MQTT \&
CoAP—are slowly forming the backbone of many IoT
infrastructures, including critical industry environments.
They are used to provide data connectivity for practically
any kind of "machines". We found out that these protocols are
affected by security and privacy issues that impact several
market verticals, applications, products, and brands.
This talk provides a security analysis of MQTT \& CoAP at the
design, implementation, and deployment level. We found issues
in the design specifications, vulnerable product
implementations, and hundreds of thousands unsecured,
open-to-the-world deployments. These issues show the risk
that endpoints could be open to denial-of-service attacks
and, in some cases, full control by an adversary. Despite the
fixes in the design specifications, it is hard for developers
to keep up with a changing standard when a technology becomes
pervasive. Also, the market of this technology is very wide
because the barrier to entry is fairly low. This led to a
multitude of fragmented implementations.
We analyzed the source code of the most common MQTT
implementations, and discovered common flaws—mostly
originating from misinterpretation of the standard. In
particular, we found issues in how multibyte strings, UTF-8
characters, and regular-expressions are parsed. Combined with
standard features that force servers to retain messages and
clients to request acknowledgement the delivery of every
message, such bugs can lead to persistent denial of service.
Our findings have been acknowledged by the MQTT Technical
Committee, which released a note to help identify the risks.
Alongside this, we've analyzed hundreds of millions MQTT \&
CoAP messages obtained from hundreds of thousands server.
Despite previous efforts that tried to raise awareness, we
still found exposed data related to various industry sectors
and sensitive information, including credentials and network
infrastructure details. Moreover, we found out that MQTT is
being used beyond messaging, to transport binary data, most
likely for OTA update purposes, which certainly raises a red
flag.
Using MQTT \& CoAP as a concrete example of modern M2M
technology, we will provide recommendations at various levels
(standardization bodies, vendors, developers, and users) in
the hope to see a significant reduction in the number of
insecure deployments in the future, and a more responsible
position by standardization bodies.},
Location = {London, UK},
URL = {https://www.blackhat.com/eu-18/briefings/schedule/#when-machines-cant-talk-security-and-privacy-issues-of-machine-to-machine-data-protocols-12722},
Date = {2018-12-06},
HowPublished = {Peer-reviewed Talk},
File = {files/talks/maggi_mqttbheu_talk_2018.pdf}
}
@TechReport{ maggi_mqttwp_tr_2018,
ShortTitle = {MQTTWP},
Author = {Maggi, Federico and Vosseler, Rainer and Quarta, Davide},
Title = {The Fragility of Industrial IoT's Data Backbone: Security
and Privacy Issues in MQTT and CoAP Protocols},
Institution = {Trend Micro, Inc.},
Abstract = {The most popular protocols for machine-tomachine (M2M)
technology---the backbone of the internet of things (IoT) and
industrial internet of things (IIoT)---are affected by
security and privacy issues that impact several market
verticals, applications, products, and brands.
This report provides a holistic security analysis of the most
popular M2M protocols: Message Queuing Telemetry Transport
(MQTT) and Constrained Application Protocol (CoAP). Given
their flexibility, these data protocols are being adopted in
a variety of settings for consumer, enterprise, and
industrial applications to connect practically all kinds of
“machine,” from innocuous fitness trackers to large power
plants. We found issues in design as well as vulnerable
implementations, along with hundreds of thousands of unsecure
deployments. These issues highlight the risk of how endpoints
could be open to denial-of-service (DoS) attacks and, in some
cases, taken advantage of to gain full control by an
attacker. Despite the fixes in the design specifications, it
is hard for developers to keep up with a changing standard
when a technology becomes pervasive. Also, the market for
this technology is very wide because the barrier to entry is
fairly low. This has led to a multitude of fragmented
implementations.
This report is aimed at raising security awareness and
driving the adoption of proper remediation measures.},
Date = {2018-12-04},
URL = {https://www.trendmicro.com/vinfo/us/security/news/internet-of-things/mqtt-and-coap-security-and-privacy-issues-in-iot-and-iiot-communication-protocols},
Series = {Research Papers},
Publisher = {Trend Micro Research},
File = {files/papers/reports/maggi_mqttwp_tr_2018.pdf}
}
@Unpublished{ maggi_webdefacementhitb_talk_2018,
ShortTitle = {WebDefacementHITB},
Author = {Maggi, Federico},
Title = {Using Machine-Learning to Investigate Web Campaigns at
Large},
EventTitle = {Hack In The Box Dubai},
Abstract = {Web defacement is the practice of altering a website after
its compromise. The altered pages, called defaced pages, can
negatively affect the reputation and business of the victim.
While investigating several campaigns, we observed that the
artifacts left by these attackers allow an expert analyst to
investigate their modus operandi and social structure, and
expand from single attacks to a group of related incidents.
However, manually performing such analysis on millions of
events is tedious, and poses scalability challenges.
From these observations, we conceived an automated system
that efficiently builds intelligence information out of raw
events. Our approach streamlines the analysts job by
automatically recognizing web campaigns, and assigning
meaningful textual labels to them. Applied to a comprehensive
dataset of 13 million incidents, our approach allowed us to
conduct what we believe been the first large-scale
investigation of this form. In addition, our approach is
meant to be adopted operationally by analysts to identify
live campaigns in the real world.
We analyze the social structure of modern web attackers,
which includes lone individuals as well as actors that
cooperate in teams. We look into their motivations, and we
draw a parallel between the time line of word-shaping events
and web campaigns, which represent the evolution of the
interests and orientation of modern attackers.},
Location = {Dubai, United Arab Emirates},
URL = {https://conference.hitb.org/hitbsecconf2018dxb/sessions/using-machine-learning-to-investigate-web-campaigns-at-large/},
Date = {2018-11-28},
HowPublished = {Peer-reviewed Talk},
File = {files/talks/maggi_webdefacementhitb_talk_2018.pdf}
}
@Unpublished{ maggi_ir_talk_2018,
ShortTitle = {IR},
Author = {Maggi, Federico},
Title = {Safety Risks and Threats in Industrial Automation Systems:
The Case of Industrial Radio Remote Controllers},
EventTitle = {Trend Micro Direction},
Location = {Tokyo, JP},
URL = {https://direction.trendmicro.com/sess/},
Date = {2018-11-16},
HowPublished = {Talk},
File = {files/talks/maggi_ir_talk_2018.pdf}
}
@InProceedings{ maggi_defplorex_2018,
ShortTitle = {DefPloreX},
Author = {Maggi, Federico and Balduzzi, Marco and Flores, Ryan and Gu,
Lion and Ciancaglini, Vincenzo},
Title = {Investigating Web Defacement Campaigns at Large},
Publisher = {ACM},
BookTitle = {Proceedings of the 2018 on Asia Conference on Computer and
Communications Security},
Series = {AsiaCCS '18},
Pages = {443--456},
Address = {New York, NY, USA},
Location = {Incheon, Republic of Korea},
Abstract = { Website defacement is the practice of altering the web
pages of a website after its compromise. The altered pages,
calleddeface pages, can negatively affect the reputation and
business of the victim site. Previous research has focused
primarily on detection, rather than exploring the defacement
phenomenon in depth. While investigating several defacements,
we observed that the artifacts left by the defacers allow an
expert analyst to investigate the actors' modus operandi and
social structure, and expand from the single deface page to a
group of related defacements (i.e., acampaign ). However,
manually performing such analysis on millions of incidents is
tedious, and poses scalability challenges. From these
observations, we propose an automated approach that
efficiently builds intelligence information out of raw deface
pages. Our approach streamlines the analysts job by
automatically recognizing defacement campaigns, and assigning
meaningful textual labels to them. Applied to a comprehensive
dataset of 13 million defacement records, from Jan. 1998 to
Sept. 2016, our approach allowed us to conduct the first
large-scale measurement on web defacement campaigns. In
addition, our approach is meant to be adopted operationally
by analysts to identify live campaigns on the field.
We go beyond confirming anecdotal evidence. We analyze the
social structure of modern defacers, which includes lone
individuals as well as actors that cooperate with each
others, or with teams, which evolve over time and dominate
the scene. We conclude by drawing a parallel between the time
line of World-shaping events and defacement campaigns,
representing the evolution of the interests and orientation
of modern defacers.},
DOI = {10.1145/3196494.3196542},
ISBN = {978-1-4503-5576-6},
Date = {2018-06-04},
File = {files/papers/conference-papers/maggi_defplorex_2018.pdf}
}
@Unpublished{ maggi_iiothmi_talk_2018,
ShortTitle = {IIoTHMI},
Author = {Maggi, Federico},
Title = {The impact of legacy machines on future manufacturing
cybersecurity},
EventTitle = {Hannover Messe},
Abstract = {Despite the focus on future-generation equipment, legacy
industrial machines will continue to exist. In terms of