explaingit

8damon/pwning-openedr

Analysis updated 2026-05-18

10C++Audience · researcherComplexity · 4/5Setup · hard

TLDR

A security research write-up documenting five confirmed high severity vulnerabilities in the OpenEDR endpoint protection software.

Mindmap

mindmap
  root((Pwning OpenEDR))
    What it does
      Vulnerability writeup
      Five confirmed findings
      Reproducible proofs
    Findings
      Service stop bypass
      Unsigned DLL load
      Memory pool increase
    Reproduction
      Isolated Windows VM
      Build all script
      Per finding scripts
    Evidence
      Screenshots
      Sysmon logs
      Pinned source hash

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Study a real-world writeup of privilege escalation and DLL hijacking flaws in security software.

USE CASE 2

Reproduce the confirmed findings in an isolated Windows VM to verify the vulnerabilities.

USE CASE 3

Reference the evidence index for logs, hashes, and screenshots supporting each advisory.

USE CASE 4

Use the pinned source commit and installer hash to test against the exact vulnerable version.

What is it built with?

C++WindowsSysmon

How does it compare?

8damon/pwning-openedrashishps1/tetris-gamebodmer/esp8266-weather-station-color
Stars101010
LanguageC++C++C++
Last pushed2017-01-112018-10-15
MaintenanceDormantDormant
Setup difficultyhardmoderatemoderate
Complexity4/52/53/5
Audienceresearcherdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires an isolated Windows VM, Visual Studio C++ build tools, and the exact pinned OpenEDR version to reproduce.

In plain English

This repository documents a set of security vulnerabilities the author found while examining OpenEDR, a piece of endpoint detection and response software that monitors a Windows computer for suspicious activity. It is a security research write-up rather than a general purpose tool, aimed at people who work in vulnerability research, penetration testing, or product security. The README lists five confirmed findings, each with a codename, an official advisory identifier, a severity score, and a plain description of what a standard, non-administrator Windows user was able to do. The impacts described include stopping the security monitoring service and clearing its queued data, tricking the genuine service into loading an unsigned file with full system privileges, causing a bounded memory usage increase, getting a system level command to run and launching a real signed kernel driver, and resetting an internal signal that controls telemetry collection. Screenshots and a full evidence folder are provided for two of the findings, including logs, hashes, and captured output. To reproduce the findings yourself, the project expects an isolated Windows virtual machine with Visual Studio's C++ build tools installed. A build script compiles all the proof of concept code, and each finding has its own reproduce script meant to be run as a standard user. One finding involves a multi-step process that requires a reboot partway through. The denial of service test is deliberately capped in size and the README warns not to run any of this against a production machine. The exact version of OpenEDR tested is pinned as a Git submodule, along with its installer hash and matching source commit, so results can be reproduced precisely. The author also ran a large batch of malformed driver calls under a Windows kernel testing tool and reports that this pass did not turn up a crash or memory corruption, while noting that this negative result does not prove the driver has no other memory safety issues.

Copy-paste prompts

Prompt 1
Explain what the FALSE FLAG finding in this repo describes and how it was demonstrated.
Prompt 2
Walk me through setting up the isolated Windows VM needed to reproduce these findings.
Prompt 3
Summarize the CVSS severity and impact of each of the five confirmed findings here.
Prompt 4
Explain what the Driver Verifier IOCTL fuzzing result in this repo does and does not prove.

Frequently asked questions

What is pwning-openedr?

A security research write-up documenting five confirmed high severity vulnerabilities in the OpenEDR endpoint protection software.

What language is pwning-openedr written in?

Mainly C++. The stack also includes C++, Windows, Sysmon.

How hard is pwning-openedr to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is pwning-openedr for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.