CVE-2024-39364
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 · uneditedAdvantech ADAM-5630 has built-in commands that can be executed without authenticating the user. These commands allow for restarting the operating system, rebooting the hardware, and stopping the execution. The commands can be sent to a simple HTTP request and are executed by the device automatically, without discrimination of origin or level of privileges of the user sending the commands.
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 · high confidenceThe Advantech ADAM-5630 IoT controller contains hardcoded unauthenticated commands accessible via HTTP that allow rebooting the OS, rebooting hardware, and stopping execution. These requests execute without any authentication, authorization, or origin verification.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 the ADAM-5630 device on your networkScan your network for devices with product identification or check the device's web interface for model information. Look for HTTP services responding on typical ports 80/443 and examine the login page or device status page for 'ADAM-5630' branding.Affected if The device is an Advantech ADAM-5630 IoT controller with an exposed HTTP interface.
-
Confirm HTTP service is accessibleAttempt to access the device's IP address via HTTP (port 80) or HTTPS (port 443) from a test system. Use a browser or curl command to see if the web interface responds.Affected if The device HTTP interface is reachable without authentication.
-
Test for unauthenticated reboot command endpointsSend HTTP GET or POST requests to common reboot endpoints such as /reboot, /cgi/reboot, or /cgi-bin/reboot using curl or similar tool. Also try the hardware reboot endpoint if discovered.Affected if HTTP requests to reboot endpoints execute without returning an authentication error or requiring credentials.
-
Test for unauthenticated execution stop commandSend HTTP requests to potential execution stop endpoints based on the device's CGI paths. Common patterns include /cgi-bin/stop, /stop, or similar endpoints mentioned in the device documentation.Affected if The execution stop command runs without any authentication challenge.
-
Verify no origin verification is enforcedSend the same reboot or stop commands from different IP addresses or with modified HTTP headers (such as missing Referer or X-Forwarded-For). Confirm the commands execute regardless of request origin.Affected if The device accepts and executes commands from any origin without validating the request source.
You are affected if you have an Advantech ADAM-5630 device with its HTTP interface exposed, where unauthenticated reboot and execution control commands are accepted without authentication or origin verification.
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 dataRestrict network access to the device using firewall rules and network segmentation. If available, apply vendor firmware updates. Otherwise, isolate the device on a dedicated OT network segment with strict access controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39364 — 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-39364 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