thinQtankLABS

Detection Engineering & Incident Response: CVE-2026-2329

Respond to an unauthenticated-RCE compromise of a Grandstream IP phone (CVE-2026-2329). Reconstruct the timeline from web and device logs, find the attacker's rogue provisioning persistence, engineer and tune a detection rule for the overflow pattern, then contain, eradicate (firmware + config), verify and report.

Intermediate 21 guided steps 6 tasks About 75 minutes Runs in your browser

Skills you will practice

  • Web and device log correlation
  • Timeline reconstruction
  • Indicators of compromise
  • Detection engineering for exploit patterns
  • Containment and eradication
  • Incident reporting

Certifications this lab maps to

This lab builds hands-on skills that appear on these certification exams. thinQtank Learning runs instructor-led training camps for each — click one to see upcoming classes.

CompTIA CySA+ CS0-003 Log analysis, detection and IR Training at thinQtank Learning EC-Council Certified Incident Handler E|CIH Incident-handling lifecycle Training at thinQtank Learning EC-Council Certified Ethical Hacker CEH Exploitation patterns and IOCs Training at thinQtank Learning ISC2 CISSP CISSP Security Operations domain Training at thinQtank Learning
Part of these certification lab packages: CySA+ CS0-003 Network+ N10-009 CISSP Certified Ethical Hacker (CEH) CEH Certified Incident Handler (E|CIH) E|CIH GCIH GCIH GCIA GCIA

The scenario

A Grandstream phone (CVE-2026-2329 open on the fleet) threw a crash-and-recover followed by a config change. The SIEM thinks it was exploited. You are the responder. Classify it.

What you will do

  1. Open and classify the incident4 steps

    Open the incident · Read the alert · Read the ticket · Classify it

  2. Reconstruct the timeline4 steps

    Pull the attacker’s requests · What status flipped to 200? · Correlate the device log · What confirms code execution?

  3. Impact and persistence3 steps

    Inspect the provisioning config · What persistence? · Record IOCs

  4. Engineer a detection rule4 steps

    Study the sample · Write a rule · Test and tune · Why endpoint + length?

  5. Contain, eradicate, verify4 steps

    Remove the rogue provisioning · Patch the firmware · Verify the device · Confirm detection holds

  6. Report2 steps

    Write the report · Why eradicate before closing?

How this lab works

A real Linux-style console. Commands run against real files, so hashes, hex dumps and comparisons give real results.

A file browser where you can place evidence into the lab, either the file provided or one of your own.

Reset a single step, a whole task or the entire lab. The environment is rebuilt so you can try again cleanly.

Progress saves after every step. Close the tab and come back later; your files and answers are waiting.