CVE-2024-45163
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Mirai botnet through 2024-08-19 mishandles simultaneous TCP connections to the CNC (command and control) server. Unauthenticated sessions remain open, causing resource consumption. For example, an attacker can send a recognized username (such as root), or can send arbitrary data.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Mirai botnet's CNC (command and control) server fails to properly manage simultaneous TCP connections from unauthenticated clients. When connections are established but not properly authenticated, the sessions remain open and consume server resources, leading to resource exhaustion that could be exploited by sending recognized usernames like 'root' or arbitrary data to keep sessions alive.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if running a Mirai CNC serverReview running processes and listening network services for binaries or services associated with Mirai botnet C2 functionality. Check for suspicious processes on port 43 or common Mirai C2 ports.Affected if The system is confirmed to be running a Mirai botnet CNC server component
-
Check for unauthenticated TCP session accumulationUse netstat or ss commands to observe established TCP connections that remain in ESTABLISHED state without corresponding authenticated sessions. Monitor for connections that persist without completing authentication flows.Affected if Large numbers of unauthenticated TCP connections accumulate and remain open beyond normal timeouts
-
Monitor for username probing patternsInspect network traffic or logs for repeated attempts to authenticate with usernames such as 'root', 'admin', or random arbitrary data being sent to maintain session liveness.Affected if Traffic logs show repeated unauthenticated connection attempts using recognized Mirai credentials or random data patterns intended to keep sessions alive
-
Check for resource exhaustion indicatorsMonitor system resources (CPU, memory, file descriptors, network sockets) for exhaustion patterns that correlate with high volumes of unauthenticated connections.Affected if System experiences resource exhaustion (socket exhaustion, memory pressure) corresponding to unauthenticated connection load
-
Verify authentication state managementReview CNC server logs or code (if accessible) for proper session cleanup after failed or incomplete authentication attempts.Affected if Sessions from unauthenticated clients are not properly terminated and cleaned up, leaving persistent zombie connections
A defender is affected if they operate a Mirai CNC server and observe unauthenticated TCP connections accumulating without proper cleanup, leading to resource exhaustion.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThis vulnerability exists within the Mirai botnet's own infrastructure; network defenders should focus on standard Mirai mitigation (blocking CNC traffic, updating IoT credentials, network segmentation) rather than expecting the botnet operators to patch their own code.
- Consultation4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45163 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45163 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data