thinQtankLABS

Detection Engineering & Incident Response: CVE-2024-23897

Respond to a Jenkins CLI arbitrary-file-read breach (CVE-2024-23897). Reconstruct the timeline from the access and read logs, see how @<path> arguments inlined master.key and credentials.xml, scope the exposure, engineer a detection rule for the @-file pattern, then contain by disabling the CLI feature, eradicate (upgrade + rotate secrets), verify and report.

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

Skills you will practice

  • Log analysis
  • detection and IR; Incident-handling lifecycle; Arbitrary file read and IOCs; Security Operations and secrets protection

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 Arbitrary file read and IOCs Training at thinQtank Learning ISC2 CISSP CISSP Security Operations and secrets protection Training at thinQtank Learning
Part of these certification lab packages: CySA+ CS0-003 CISSP Certified Ethical Hacker (CEH) CEH Certified Incident Handler (E|CIH) E|CIH GCIH GCIH GCIA GCIA

The scenario

A Jenkins controller (CVE-2024-23897 open) logged unauthenticated CLI calls with @ arguments that returned the contents of secret files. 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 timeline3 steps

    Pull the attacker’s requests · Correlate the read log · What is the impact?

  3. Scope the exposure3 steps

    Inspect the exposed files list · What must be rotated? · Record IOCs

  4. Engineer a detection rule4 steps

    Study the sample · Write a rule · Test and tune · Why not flag every @?

  5. Contain, eradicate, verify5 steps

    Contain: disable the CLI feature · Upgrade Jenkins · Rotate the exposed secrets · Verify the host · …

  6. Report2 steps

    Write the report · Why rotate, not just patch?

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.