☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
CVSS: 7.5 🐛 CWE-400
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2024-34084

CVE-2024-34084 Denial of Service in Minder
📅 PUBLISHED: 2024-05-07 14:12 UTC 🔄 UPDATED: 2026-09-23 20:19 UTC
[ OFFICIAL PATCH DEPLOYED ↓ ] FIX: LIKELY — 2 independent sources confirm fix
[ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.59%
👁️
0.59% probability
14.8× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
Patch available — upgrade to latest release
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
7.5
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-34084 is a high-severity Denial of Service (DoS) vulnerability in Minder, an open-source software supply chain security platform. The flaw resides in the HandleGithubWebhook function, which processes incoming GitHub webhook events. An unauthenticated attacker can send a specially crafted HTTP request to this endpoint, causing the Minder controlplane to crash before the request is validated. This results in a complete denial of service for all legitimate users. The vulnerability has a CVSS score of 7.5 and is fixed in version 0.0.48. No public proof-of-concept (PoC) or exploit code is currently available, but the attack surface is exposed to any network that can reach the webhook endpoint.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

Minder is a Go-based application. The vulnerability is in the core controlplane component, not in a specific package manager. However, organizations using Minder to secure their software supply chain are at risk, as an attacker could disrupt the platform's ability to monitor and enforce security policies.

CVSS Breakdown & Threat Level

  • CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
  • Base Score: 7.5 (High)
  • Attack Vector (AV): Network – The vulnerability is exploitable remotely.
  • Attack Complexity (AC): Low – No special conditions are required.
  • Privileges Required (PR): None – No authentication is needed.
  • User Interaction (UI): None – No user action is required.
  • Scope (S): Unchanged – The exploit does not affect other components.
  • Confidentiality (C): None – No data is exposed.
  • Integrity (I): None – No data is modified.
  • Availability (A): High – The controlplane is completely disrupted.

Threat Level: High. The low attack complexity and lack of authentication make this a serious threat for any exposed Minder instance.

Deep Dive & Mechanics

The vulnerability is a classic resource exhaustion (CWE-400) issue. The HandleGithubWebhook function in Minder's controlplane is designed to receive and process GitHub webhook events. The flaw occurs because the function attempts to parse or process the incoming HTTP request before performing any validation (e.g., verifying the webhook secret or checking the request's origin). An attacker can send a malformed or oversized HTTP request that triggers an unhandled panic or excessive resource consumption in the parsing logic, causing the entire controlplane process to crash.

The crash is not a simple error; it is a denial of service that prevents the controlplane from handling any further requests, including legitimate webhook events from GitHub. This means an attacker can repeatedly crash the service, effectively taking it offline.

Vulnerable vs. Patched Code

The exact code changes are not publicly available, but the fix in version 0.0.48 likely involves moving the request validation logic to the beginning of the HandleGithubWebhook function. This ensures that only validated, trusted requests are processed, preventing malformed data from reaching the vulnerable parsing code.

Vulnerable (conceptual):

func HandleGithubWebhook(w http.ResponseWriter, r *http.Request) {
    // Process request body immediately
    body, _ := ioutil.ReadAll(r.Body)
    // Parse webhook payload (vulnerable to malformed data)
    event, _ := github.ParseWebHook(github.WebHookType(r), body)
    // ... later validation
}

Patched (conceptual):

func HandleGithubWebhook(w http.ResponseWriter, r *http.Request) {
    // Validate request first
    payload, err := github.ValidatePayload(r, []byte(webhookSecret))
    if err != nil {
        http.Error(w, "invalid payload", http.StatusBadRequest)
        return
    }
    // Now process the validated payload
    event, _ := github.ParseWebHook(github.WebHookType(r), payload)
    // ... rest of logic
}

Exploitation & Lab Setup

Red Team (Offensive)

Prerequisites:

  • A target Minder controlplane with the webhook endpoint exposed (e.g., https://minder.example.com/api/v1/webhook/github).
  • Ability to send HTTP requests to that endpoint.

Exploitation Steps:

  1. Identify the endpoint: Scan for the /api/v1/webhook/github path or similar.
  2. Craft a malformed request: Send an HTTP POST request with a malformed body (e.g., extremely large payload, invalid JSON, or a request that triggers a panic).
  3. Send the request: Use curl or a custom script to send the request repeatedly.

Example (conceptual):

curl -X POST https://minder.example.com/api/v1/webhook/github \
  -H "Content-Type: application/json" \
  -d '{"invalid": "data"}' \
  --raw

Impact: The controlplane crashes, denying service to all users.

Blue Team (Defensive)

Detection:

  • Monitor for a high rate of HTTP 500 errors or connection resets from the webhook endpoint.
  • Look for logs indicating a panic or crash in the Minder controlplane.
  • Use the detection rules below.

Mitigation:

  • Immediately upgrade to Minder 0.0.48 or later.
  • If upgrading is not possible, restrict network access to the webhook endpoint using a firewall or reverse proxy (e.g., only allow GitHub's IP ranges).
  • Implement a Web Application Firewall (WAF) rule to block malformed requests.

Indicators of Compromise (IOCs)

  • Network:
    • Repeated HTTP POST requests to /api/v1/webhook/github with malformed payloads.
    • High volume of HTTP 500 responses from the Minder controlplane.
  • Logs:
    • Panic messages in Minder logs (e.g., panic: runtime error).
    • Log entries showing HandleGithubWebhook failing before validation.
  • System:
    • Minder controlplane process crashing and restarting frequently.

Detection Engineering

YARA Rule

rule minder_webhook_dos_attempt {
    meta:
        description = "Detects malformed HTTP requests targeting Minder webhook endpoint"
        author = "Valters IT"
        date = "2024-01-01"
        reference = "CVE-2024-34084"
    strings:
        $webhook_path = "/api/v1/webhook/github"
        $panic_string = "panic:"
        $invalid_payload = "invalid"
    condition:
        $webhook_path and ($panic_string or $invalid_payload)
}

Sigma Rule

title: Minder Webhook DoS Attempt
id: 12345678-1234-1234-1234-123456789012
status: experimental
description: Detects attempts to exploit CVE-2024-34084 by sending malformed requests to Minder webhook endpoint
author: Valters IT
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-uri-stem: "/api/v1/webhook/github"
        sc-status: 500
    condition: selection
falsepositives:
    - Legitimate webhook failures due to network issues
level: high

Suricata Rule

alert http any any -> any any (msg:"Minder Webhook DoS Attempt"; flow:to_server; content:"POST"; http_method; content:"/api/v1/webhook/github"; http_uri; pcre:"/(panic|invalid)/i"; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate:

  1. Upgrade: Update Minder to version 0.0.48 or later.
  2. Network Restriction: If immediate upgrade is not possible, restrict access to the webhook endpoint to only GitHub's IP ranges (see GitHub's meta API).
  3. WAF Rule: Deploy a WAF rule to block requests with malformed payloads or excessive size.

Long-term:

  • Implement input validation at the earliest possible point in all webhook handlers.
  • Use a reverse proxy (e.g., Nginx) to perform basic validation before forwarding requests to the controlplane.
  • Monitor for similar vulnerabilities in other components.

Valters IT Signature This report was generated by Valters IT DevSecOps AI. For questions, contact security@valters-it.com.

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-34084/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.