@inproceedings{PuschnerSaatjohannWillingetal.2021, author = {Puschner, Endres and Saatjohann, Christoph and Willing, Markus and Dresen, Christian and K{\"o}be, Julia and Rath, Benjamin and Paar, Christof and Eckardt, Lars and Haverkamp, Uwe and Schinzel, Sebastian}, title = {Listen to Your Heart: Evaluation of the Cardiologic Ecosystem}, series = {ARES 2021: The 16th International Conference on Availability, Reliability and Security}, booktitle = {ARES 2021: The 16th International Conference on Availability, Reliability and Security}, doi = {10.1145/3465481.3465753}, url = {http://nbn-resolving.de/urn:nbn:de:hbz:836-opus-139012}, year = {2021}, abstract = {Modern implantable cardiologic devices communicate via radio frequency techniques and nearby gateways to a backend server on the internet. Those implanted devices, gateways, and servers form an ecosystem of proprietary hardware and protocols that process sensitive medical data and is often vital for patients' health. This paper analyzes the security of this Ecosystem, from technical gateway aspects, via the programmer, to configure the implanted device, up to the processing of personal medical data from large cardiological device producers. Based on a real-world attacker model, we evaluated different devices and found several severe vulnerabilities. Furthermore, we could purchase a fully functional programmer for implantable cardiological devices, allowing us to re-program such devices or even induce electric shocks on untampered implanted devices. Additionally, we sent several Art. 15 and Art. 20 GDPR inquiries to manufacturers of implantable cardiologic devices, revealing non-conforming processes and a lack of awareness about patients' rights and companies' obligations. This, and the fact that many vulnerabilities are still to be found after many vulnerability disclosures in recent years, present a worrying security state of the whole ecosystem.}, language = {en} } @inproceedings{EbbersIsingSaatjohannetal.2021, author = {Ebbers, Simon and Ising, Fabian and Saatjohann, Christoph and Schinzel, Sebastian}, title = {Grand Theft App: Digital Forensics of Vehicle Assistant Apps}, series = {ARES 2021: The 16th International Conference on Availability, Reliability and Security}, booktitle = {ARES 2021: The 16th International Conference on Availability, Reliability and Security}, doi = {10.1145/3465481.3465754}, url = {http://nbn-resolving.de/urn:nbn:de:hbz:836-opus-139031}, year = {2021}, abstract = {Due to the increasing connectivity of modern vehicles, collected data is no longer only stored in the vehicle itself but also transmitted to car manufacturers and vehicle assistant apps. This development opens up new possibilities for digital forensics in criminal investigations involving modern vehicles. This paper deals with the digital forensic analysis of vehicle assistant apps of eight car manufacturers. We reconstruct the driver's activities based on the data stored on the smartphones and in the manufacturer's backend. For this purpose, data of the Android and iOS apps of the car manufacturers Audi, BMW, Ford, Mercedes, Opel, Seat, Tesla, and Volkswagen were extracted from the smartphone and examined using digital forensic methods following forensics guidelines. Additionally, manufacturer data was retrieved using Subject Access Requests. Using the extensive data gathered, we reconstruct trips and refueling processes, determine parking positions and duration, and track the locking and unlocking of the vehicle. Our findings show that the digital forensic investigation of smartphone applications is a useful addition to vehicle forensics and should therefore be taken into account in the strategic preparation of future digital forensic investigations.}, language = {en} } @inproceedings{PoddebniakIsingBoecketal.2021, author = {Poddebniak, Damian and Ising, Fabian and B{\"o}ck, Hanno and Schinzel, Sebastian}, title = {Why TLS is better without STARTTLS: A Security Analysis of STARTTLS in the Email Context}, series = {Proceedings of the 30th USENIX Security Symposium, August 11-13, 2021}, volume = {2021}, booktitle = {Proceedings of the 30th USENIX Security Symposium, August 11-13, 2021}, isbn = {978-1-939133-24-3}, year = {2021}, abstract = {TLS is one of today's most widely used and best-analyzed encryption technologies. However, for historical reasons, TLS for email protocols is often not used directly but negotiated via STARTTLS. This additional negotiation adds complexity and was prone to security vulnerabilities such as naive STARTTLS stripping or command injection attacks in the past. We perform the first structured analysis of STARTTLS in SMTP, POP3, and IMAP and introduce EAST, a semi-automatic testing toolkit with more than 100 test cases covering a wide range of variants of STARTTLS stripping, command and response injections, tampering attacks, and UI spoofing attacks for email protocols. Our analysis focuses on the confidentiality and integrity of email submission (email client to SMTP server) and email retrieval (email client to POP3 or IMAP server). While some of our findings are also relevant for email transport (from one SMTP server to another), the security implications in email submission and retrieval are more critical because these connections involve not only individual email messages but also user credentials that allow access to a user's email archive. We used EAST to analyze 28 email clients and 23 servers. In total, we reported over 40 STARTTLS issues, some of which allow mailbox spoofing, credential stealing, and even the hosting of HTTPS with a cross-protocol attack on IMAP. We conducted an Internet-wide scan for the particularly dangerous command injection attack and found that 320.000 email servers (2\% of all email servers) are affected. Surprisingly, several clients were vulnerable to STARTTLS stripping attacks. In total, only 3 out of 28 clients did not show any STARTTLS-specific security issues. Even though the command injection attack received multiple CVEs in the past, EAST detected eight new instances of this problem. In total, only 7 out of 23 tested servers were never affected by this issue. We conclude that STARTTLS is error-prone to implement, under-specified in the standards, and should be avoided.}, language = {en} } @article{BrinkmannDresenMergetetal.2021, author = {Brinkmann, Marcus and Dresen, Christian and Merget, Robert and Poddebniak, Damian and M{\"u}ller, Jens and Somorovsky, Juraj and Schwenk, J{\"o}rg and Schinzel, Sebastian}, title = {ALPACA: Application Layer Protocol Confusion - Analyzing and Mitigating Cracks in TLS Authentication}, series = {30th USENIX Security Symposium}, journal = {30th USENIX Security Symposium}, year = {2021}, language = {en} } @inproceedings{WillingSaatjohannRathetal.2021, author = {Willing, Markus and Saatjohann, Christoph and Rath, Benjamin and Schinzel, Sebastian and Eckardt, Lars and K{\"o}be, Julia}, title = {Experiences with General Data Protection Regulations and Remote Monitoring of Implantable Rhythm Devices}, series = {87. Jahrestagung der Deutsche Gesellschaft f{\"u}r Kardiologie - Herz‑ und Kreislauforschung e.V}, booktitle = {87. Jahrestagung der Deutsche Gesellschaft f{\"u}r Kardiologie - Herz‑ und Kreislauforschung e.V}, publisher = {Springer-Verlag GmbH}, doi = {10.1007/s00392-021-01843-w}, year = {2021}, language = {en} } @article{WillingDresenGerlitzetal.2021, author = {Willing, Markus and Dresen, Christian and Gerlitz, Eva and Haering, Maximilian and Smith, Matthew and Binnewies, Carmen and Guess, Tim and Haverkamp, Uwe and Schinzel, Sebastian}, title = {Behavioral responses to a cyber attack in a hospital environment}, series = {Nature -- Scientific Reports}, journal = {Nature -- Scientific Reports}, doi = {10.1038/s41598-021-98576-7}, year = {2021}, abstract = {Technical and organizational steps are necessary to mitigate cyber threats and reduce risks. Human behavior is the last line of defense for many hospitals and is considered as equally important as technical security. Medical staff must be properly trained to perform such procedures. This paper presents the first qualitative, interdisciplinary research on how members of an intermediate care unit react to a cyberattack against their patient monitoring equipment. We conducted a simulation in a hospital training environment with 20 intensive care nurses. By the end of the experiment, 12 of the 20 participants realized the monitors' incorrect behavior. We present a qualitative behavior analysis of high performing participants (HPP) and low performing participants (LPP). The HPP showed fewer signs of stress, were easier on their colleagues, and used analog systems more often than the LPP. With 40\% of our participants not recognizing the attack, we see room for improvements through the use of proper tools and provision of adequate training to prepare staff for potential attacks in the future.}, language = {en} } @inproceedings{SaatjohannIsingGierlingsetal.2022, author = {Saatjohann, Christoph and Ising, Fabian and Gierlings, Matthias and Noss, Dominik and Schimmler, Sascha and Klemm, Alexander and Grundmann, Leif and Frosch, Tilman and Schinzel, Sebastian}, title = {Sicherheit medizintechnischer Protokolle im Krankenhaus}, series = {SICHERHEIT 2022. Hrsg. Christian Wressnegger, Delphine Reinhardt, Thomas Barber, Bernhard C. Witt, Daniel Arp, Zoltan Mann}, booktitle = {SICHERHEIT 2022. Hrsg. Christian Wressnegger, Delphine Reinhardt, Thomas Barber, Bernhard C. Witt, Daniel Arp, Zoltan Mann}, publisher = {Gesellschaft f{\"u}r Informatik e.V.}, address = {Bonn}, isbn = {978-3-88579-717-3}, issn = {1617-5468}, doi = {10.18420/sicherheit2022_09}, url = {http://nbn-resolving.de/urn:nbn:de:hbz:836-opus-150072}, year = {2022}, abstract = {Medizinische Einrichtungen waren in den letzten Jahren immer wieder von Cyber-Angriffen betroffen. Auch wenn sich diese Angriffe derzeit auf die Office-IT-Infrastruktur der Einrichtungen konzentrieren, existiert mit medizinischen Systemen und Kommunikationsprotokollen eine weitere wenig beachtete Angriffsoberfl{\"a}che. In diesem Beitrag analysieren wir die weit verbreiteten medizintechnischen Kommunikations-Protokolle DICOM und HL7 sowie Protokoll-Implementierungen auf ihre IT-Sicherheit. Daf{\"u}r pr{\"a}sentieren wir die Ergebnisse der Sicherheitsanalyse der DICOM- und HL7-Standards, einen Fuzzer "MedFUZZ" f{\"u}r diese Protokolle sowie einen Schwachstellenscanner "MedVAS", der Schwachstellen in medizintechnischen Produktivumgebungen auffinden kann.}, language = {de} } @inproceedings{MayerPoddebniakFischeretal.2022, author = {Mayer, Peter and Poddebniak, Damian and Fischer, Konstantin and Brinkmann, Marcus and Somorovsky, Juraj and Schinzel, Sebastian and Volkamer, Melanie}, title = {"I don't know why I check this...'' - Investigating Expert Users' Strategies to Detect Email Signature Spoofing Attacks}, series = {Eighteenth Symposium on Usable Privacy and Security (SOUPS 2022)}, booktitle = {Eighteenth Symposium on Usable Privacy and Security (SOUPS 2022)}, publisher = {USENIX Association}, address = {Boston, MA}, isbn = {978-1-939133-30-4}, pages = {77 -- 96}, year = {2022}, abstract = {OpenPGP is one of the two major standards for end-to-end email security. Several studies showed that serious usability issues exist with tools implementing this standard. However, a widespread assumption is that expert users can handle these tools and detect signature spoofing attacks. We present a user study investigating expert users' strategies to detect signature spoofing attacks in Thunderbird. We observed 25 expert users while they classified eight emails as either having a legitimate signature or not. Studying expert users explicitly gives us an upper bound of attack detection rates of all users dealing with PGP signatures. 52\% of participants fell for at least one out of four signature spoofing attacks. Overall, participants did not have an established strategy for evaluating email signature legitimacy. We observed our participants apply 23 different types of checks when inspecting signed emails, but only 8 of these checks tended to be useful in identifying the spoofed or invalid signatures. In performing their checks, participants were frequently startled, confused, or annoyed with the user interface, which they found supported them little. All these results paint a clear picture: Even expert users struggle to verify email signatures, usability issues in email security are not limited to novice users, and developers may need proper guidance on implementing email signature GUIs correctly.}, language = {en} } @inproceedings{IsingPoddebniakKappertetal.2023, author = {Ising, Fabian and Poddebniak, Damian and Kappert, Tobias and Saatjohann, Christoph and Schinzel, Sebastian}, title = {Content-Type: multipart/oracle -- Tapping into Format Oracles in Email End-to-End Encryption}, series = {32nd USENIX Security Symposium}, booktitle = {32nd USENIX Security Symposium}, publisher = {USENIX Association}, year = {2023}, abstract = {S/MIME and OpenPGP use cryptographic constructions repeatedly shown to be vulnerable to format oracle attacks in protocols like TLS, SSH, or IKE. However, format oracle attacks in the End-to-End Encryption (E2EE) email setting are considered impractical as victims would need to open many attacker-modified emails and communicate the decryption result to the attacker. But is this really the case? In this paper, we survey how an attacker may remotely learn the decryption state in email E2EE. We analyze the interplay of MIME and IMAP and describe side-channels emerging from network patterns that leak the decryption status in Mail User Agents (MUAs). Concretely, we introduce specific MIME trees that produce decryption-dependent net work patterns when opened in a victim's email client. We survey 19 OpenPGP- and S/MIME-enabled email clients and four cryptographic libraries and uncover a side-channel leaking the decryption status of S/MIME messages in one client. Further, we discuss why the exploitation in the other clients is impractical and show that it is due to missing feature support and implementation quirks. These unintended defenses create an unfortunate conflict between usability and security. We present more rigid countermeasures for MUA developers and the standards to prevent exploitation.}, language = {en} } @inproceedings{SaatjohannIsingSchinzel2024, author = {Saatjohann, Christoph and Ising, Fabian and Schinzel, Sebastian}, title = {KIM: Kaos In der Medizin}, series = {Sicherheit, Schutz und Zuverl{\"a}ssigkeit: Konferenzband der 12. Jahrestagung des Fachbereichs Sicherheit der Gesellschaft f{\"u}r Informatik e.V. (GI)}, booktitle = {Sicherheit, Schutz und Zuverl{\"a}ssigkeit: Konferenzband der 12. Jahrestagung des Fachbereichs Sicherheit der Gesellschaft f{\"u}r Informatik e.V. (GI)}, doi = {10.25974/fhms-17807}, url = {http://nbn-resolving.de/urn:nbn:de:hbz:836-opus-178072}, year = {2024}, abstract = {Die sichere E-Mail-Infrastruktur f{\"u}r {\"A}rzt*innen, Apotheker*innen, Krankenversicherungen und Kliniken in Deutschland, KIM - Kommunikation im Gesundheitswesen - ist mit {\"u}ber 200 Millionen E-Mails in den vergangenen zwei Jahren eine der am meisten genutzten Anwendungen in der Telematikinfrastruktur. Mit dem Ausgeben von S/MIME-Zertifikaten f{\"u}r alle medizinische Beteiligten in Deutschland verspricht KIM sichere Ende-zu-Ende-Verschl{\"u}sselung von E-Mails zwischen Heilberufler*innen in ganz Deutschland. In diesem Paper analysieren wir die KIM-Spezifikation sowie eine beispielhafte KIM-Installation in einer deutschen Zahnarztpraxis. Wir zeigen, dass KIM kryptografisch ein sehr hohes Sicherheitslevel erf{\"u}llt, doch in der Verarbeitung der E-Mails bei den Clients eine schwerwiegende Sicherheitsl{\"u}cke besteht. Weiterhin zeigen wir zwei Sicherheitsl{\"u}cken in dem KIM-Verarbeitungsmodul eines großen deutschen Unternehmens f{\"u}r medizinische Software. Diese Defizite zeigen außerdem M{\"a}ngel in dem verpflichtenden Zulassungsprozess der KIM-Komponenten auf.}, language = {de} }