Demo Data from EDBT 2026 / reviewers in the wild / expert
Florian Schweins
dblp:308/6016
· DBLP profile ↗
2ranked-venue papers
1as first author
2since 2021 · last 2025
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Security and privacy · 2 · 1 first-author · 2 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Network and information security
1 paper |
Cryptographic primitives and cryptanalysis · 67% Hardware security and side channels · 33% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Electronic design automation · 100% |
Topics — the 3 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Hardware security and side channels
intellectual property protection |
0.6 | 1 | 2022 | How Not to Protect Your IP - An Industry-Wide Break of IEEE 1735 Implementations · SP 2022 |
Cryptographic primitives and cryptanalysis › cryptanalysis
key recovery attack |
0.6 | 1 | 2022 | How Not to Protect Your IP - An Industry-Wide Break of IEEE 1735 Implementations · SP 2022 |
Cryptographic primitives and cryptanalysis › cryptographic implementation
white-box cryptography |
0.6 | 1 | 2022 | How Not to Protect Your IP - An Industry-Wide Break of IEEE 1735 Implementations · SP 2022 |
Methods — techniques the papers use, named apart from their topics
white-box analysis · 1.1RSA cryptanalysis · 1.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | VMIGEN: Utilizing Virtual Machine Introspection for Fuzzing Complex Closed-Source TargetsabstractModern fuzzing is a highly successful testing method, but it still struggles with stateful software that expects complex, context-rich inputs. Instead of further tuning the fuzzing process itself, we introduce VMIGEN, a new approach that captures interactions by implicitly recording both complex inputs and the corresponding system states needed for effective testing. By using Virtual Machine Introspection (VMI), a technique for observing the state and behavior of a VM from the outside, we can monitor actual runtime events for a given system. This way, we can extract concrete inputs and snapshot the whole system at relevant interactions to preserve the full system state, thereby enabling effective fuzzing. At the same time, our approach does not require access to source code, allowing us to test closed-source software on Windows. To demonstrate VMIGEN's effectiveness, we use it to test kernel drivers, including those of anti-virus engines, and Remote Procedure Call (RPC) interfaces. Our comprehensive evaluation shows that our VMI-based method enables an existing fuzzer to achieve up to 6.6x more code coverage. In total, VMIGEN allowed us to discover 33 previously unknown bugs, which we disclosed in a coordinated way to the affected vendors. Florian Schweins, Moritz Schloegel, Moritz Bley, Nico Schiller, Thorsten Holz |
ACSAC | 1 |
| 2022 | How Not to Protect Your IP - An Industry-Wide Break of IEEE 1735 ImplementationsabstractModern hardware systems are composed of a variety of third-party Intellectual Property (IP) cores to implement their overall functionality. Since hardware design is a globalized process involving various (untrusted) stakeholders, a secure management of the valuable IP between authors and users is inevitable to protect them from unauthorized access and modification. To this end, the widely adopted IEEE standard 1735-2014 was created to ensure confidentiality and integrity. In this paper, we outline structural weaknesses in IEEE 1735 that cannot be fixed with cryptographic solutions (given the contemporary hardware design process) and thus render the standard inherently insecure. We practically demonstrate the weaknesses by recovering the private keys of IEEE 1735 implementations from major Electronic Design Automation (EDA) tool vendors, namely Intel, Xilinx, Cadence, Siemens, Microsemi, and Lattice, while results on a seventh case study are withheld. As a consequence, we can decrypt, modify, and re-encrypt all allegedly protected IP cores designed for the respective tools, thus leading to an industry-wide break. As part of this analysis, we are the first to publicly disclose three RSA-based white-box schemes that are used in real-world products and present cryptanalytical attacks for all of them, finally resulting in key recovery. Julian Speith, Florian Schweins, Maik Ender, Marc Fyrbiak, Alexander May 0001, Christof Paar |
SP | 2 |