Skip to main navigation Skip to search Skip to main content

The case of the poisoned event handler: Weaknesses in the node.js event-driven architecture

  • Virginia Polytechnic Institute and State University

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

13 Scopus citations

Abstract

Node.js has seen rapid adoption in industry and the open- source community. Unfortunately, its event-driven architec- ture exposes Node.js applications to Event Handler-Poisoning denial of service attacks. Our evaluation of the state of prac- tice in Node.js| combining a study of 353 publicly reported security vulnerabilities and a survey of 151 representative npm modules | demonstrates that the community is not equipped to combat this class of attack. We recommend several changes to the state of practice and propose both programming language and runtime approaches to defend against Event Handler-Poisoning attacks.

Original languageEnglish
Title of host publicationProceedings of the 10th European Workshop on Systems Security, EuroSec 2017, co-located with European Conference on Computer Systems, EuroSys 2017
PublisherAssociation for Computing Machinery
ISBN (Print)9781450349352
DOIs
StatePublished - Apr 23 2017
Event10th European Workshop on Systems Security, EuroSec 2017, co-located with European Conference on Computer Systems, EuroSys 2017 - Belgrade, Serbia
Duration: Apr 23 2017Apr 27 2017

Publication series

NameProceedings of the Proceedings of the 10th European Workshop on Systems Security, EuroSec 2017, co-located with European Conference on Computer Systems, EuroSys 2017

Conference

Conference10th European Workshop on Systems Security, EuroSec 2017, co-located with European Conference on Computer Systems, EuroSys 2017
Country/TerritorySerbia
CityBelgrade
Period04/23/1704/27/17

Keywords

  • Denial of service
  • Event-driven architecture
  • Node.js
  • ReDoS

Fingerprint

Dive into the research topics of 'The case of the poisoned event handler: Weaknesses in the node.js event-driven architecture'. Together they form a unique fingerprint.

Cite this