Security technologies often fail not because they are ineffective, but because they are difficult to integrate into existing systems. "Making security tools easier to use is just as crucial as ensuring their technical robustness," says Sabine Houy, the developer behind the new solution, CFIghter. ImageVictoria Skeidsvoll

This article is from Umeå University website. Text and image: Victoria Skeidsvoll

Modern and powerful security technology that protects against hacking attempts is used to a very limited extent – despite having been available to developers for more than a decade. Researchers at Umeå University can now reveal why the technology fails to take hold.

“At the same time, we present an automated solution that makes it easy to adopt the technology,” says Sabine Houy, WASP doctoral student at the Department of Computing Science, who is now defending her thesis.

In common operating systems such as Windows and Android, as well as in browsers like Chrome and Edge, there is a built‑in security mechanism – Control Flow Integrity, CFI. It prevents attackers from hijacking software by exploiting bugs or memory errors, particularly in programmes written in languages such as C and C++.

“Attackers can use such flaws to redirect the programme flow and execute malicious code,” explains Sabine Houy, doctoral student at the Department of Computing Science, Umeå University.

Despite the technology being well established and technically mature, its use is surprisingly low.

“Less than one per cent of software packages in major Linux distributions use CFI. Even Android has only enabled the technology for selected components, which is remarkable. CFI provides robust guardrails and has been available for over a decade,” says Sabine Houy.

Automated solution to a complex problem

In her research, Houy investigated why this is the case. When she and her colleagues attempted to enable CFI in OpenJDK – the open‑source version of Java – they quickly encountered extensive problems. The software refused to compile, crashed, or behaved unpredictably.

“Solving the issues required extensive manual work to understand why the security tool clashed with the way the software was built,” says Sabine Houy. She argues that the problem is not that CFI does not work.
“It is that real‑world software is complex and often violates the assumptions that CFI relies on,” says Sabine Houy.

Directly crucial for security in critical systems

To address this, Houy now introduces a tool that automatically detects and repairs these compatibility issues, called CFIghter. “In tests on real software projects, our solution succeeded in enabling CFI where manual attempts would have been both time‑consuming and technically difficult.”

The results have immediate relevance for software security in critical environments. Operating systems, browsers and industrial control systems all use programming languages that CFI can protect. Automated tools can help companies implement security measures at scale – something that is becoming increasingly important as cyberattacks grow more sophisticated.

“Developers want to use security technologies, but the threshold becomes too high when the tools do not work out of the box. This provides a smart and safe solution that reduces the burden,” says Sabine Houy.

CFI will not eliminate all security risks. “But by making it more accessible, one can significantly raise the bar for attackers exploiting memory vulnerabilities in critical software systems,” concludes Sabine Houy.

Prominent research

Sabine Houy has worked with both theoretical and practical aspects of CFI. In her master’s thesis, she also worked on security aspects of cryptocurrency ledgers. Sabine Houy is part of the prominent research group Software Engineering and Security at Umeå University, led by Professor Alexandre Bartel at the Department of Computing Science. He has recently received several prestigious international awards. He also teaches the highly popular course in Computer Security, as well as the Reverse Engineering course, which includes the study of malware.


Published: February 19th, 2026

[addtoany]

Latest news

We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners. View more
Cookies settings
Accept
Privacy & Cookie policy
Privacy & Cookies policy
Cookie name Active
The WASP website wasp-sweden.org uses cookies. Cookies are small text files that are stored on a visitor’s computer and can be used to follow the visitor’s actions on the website. There are two types of cookie:
  • permanent cookies, which remain on a visitor’s computer for a certain, pre-determined duration,
  • session cookies, which are stored temporarily in the computer memory during the period under which a visitor views the website. Session cookies disappear when the visitor closes the web browser.
Permanent cookies are used to store any personal settings that are used. If you do not want cookies to be used, you can switch them off in the security settings of the web browser. It is also possible to set the security of the web browser such that the computer asks you each time a website wants to store a cookie on your computer. The web browser can also delete previously stored cookies: the help function for the web browser contains more information about this. The Swedish Post and Telecom Authority is the supervisory authority in this field. It provides further information about cookies on its website, www.pts.se.
Save settings
Cookies settings