CVE-2024-38308
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 5550's web application includes a "logs" page where all the HTTP requests received are displayed to the user. The device doesn't correctly neutralize malicious code when parsing HTTP requests to generate page output.
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 confidenceAdvantech ADAM 5550 industrial controller's web application has a reflected XSS vulnerability in the logs page. The device fails to properly sanitize or encode HTTP request data before displaying it in the logs output, allowing attackers to inject malicious JavaScript through crafted HTTP requests that will execute when an administrator views the logs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm ADAM 5550 device identityAccess the device's web interface or check the device label/marketing materials for the model number ADAM 5550. Alternatively, use network scanning to identify the device through its HTTP banner or HTML title page which typically displays the model name.Affected if The device is an Advantech ADAM 5550 industrial controller.
-
Identify firmware versionLog into the ADAM 5550 web interface and navigate to the System or Information section, typically found under a 'System Info' or 'Device Status' page. The firmware version is usually displayed there.Affected if Any firmware version is installed since all versions are affected.
-
Verify web interface accessibilityAttempt to access the device's web interface via HTTP/HTTPS using the device IP address. Confirm the login page or device status page loads successfully.Affected if The web interface is reachable on the network.
-
Confirm logs page is accessibleAfter logging into the web interface, navigate to the logs or log viewer page. This is typically found under sections named 'Logs', 'Event Log', 'System Log', or 'Data Log'.Affected if The logs page is accessible and displays log entries.
-
Test for reflected XSS in logs pageUsing a web browser or HTTP client, submit a crafted HTTP request to the device with a test XSS payload in a parameter that might be reflected in the logs (such as a search parameter or filter field). Then view the logs page to see if the payload executes as JavaScript.Affected if The injected script content appears unescaped in the logs output and executes in the browser when viewing the page.
If the device is an Advantech ADAM 5550 with an accessible web interface and the logs page reflects unsanitized input, the environment is affected by this reflected XSS vulnerability.
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 dataApply the vendor-provided firmware update when available. Until then, restrict network access to the device's web interface using firewall rules or network segmentation to limit exposure to untrusted users.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38308 — 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-38308 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