CVE-2020-15809
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 · uneditedspxmanage on certain SpinetiX devices allows requests that access unintended resources because of SSRF and Path Traversal. This affects HMP350, HMP300, and DiVA through 4.5.2-1.0.36229; HMP400 and HMP400W through 4.5.2-1.0.2-1eb2ffbd; and DSOS through 4.5.2-1.0.2-1eb2ffbd.
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 spxmanage component in SpinetiX digital signage devices (HMP350, HMP300, DiVA, HMP400, HMP400W, DSOS) contains SSRF and Path Traversal vulnerabilities allowing attackers to make requests that access unintended resources via crafted malicious requests.
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 data<= 4.5.2-1.0.2-1eb2ffbd<= 4.5.2-1.0.36229<= 4.5.2-1.0.36229<= 4.5.2-1.0.36229<= 4.5.2-1.0.2-1eb2ffbd<= 4.5.2-1.0.2-1eb2ffbdCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify the SpinetiX device modelAccess the device web interface or check the device label to determine if it is an HMP350, HMP300, DiVA, HMP400, HMP400W, or DSOS unitAffected if The device is any of these six models listed in the affected products
-
Check firmware version on HMP350/HMP300/DiVA devicesLog into the device admin interface and navigate to System > Maintenance or Settings > About to view the firmware version numberAffected if The firmware version is 4.5.2-1.0.36229 or lower (for HMP350, HMP300, or DiVA)
-
Check firmware version on HMP400/HMP400W/DSOS devicesLog into the device admin interface and navigate to System > Maintenance or Settings > About to view the firmware version numberAffected if The firmware version is 4.5.2-1.0.2-1eb2ffbd or lower (for HMP400, HMP400W, or DSOS)
-
Verify spxmanage component exposureCheck if the spxmanage web endpoint is accessible on the device (typically at /spxmanage or /admin/spxmanage) - review network firewall rules and device access controlsAffected if The spxmanage component is exposed to untrusted networks and the device firmware matches the affected version ranges above
A device is affected if it is an HMP350, HMP300, DiVA, HMP400, HMP400W, or DSOS unit running firmware at or below the version thresholds (4.5.2-1.0.36229 for HMP350/HMP300/DiVA; 4.5.2-1.0.2-1eb2ffbd for HMP400/HMP400W/DSOS) with the spxmanage component accessible to attackers.
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 dataUpdate affected devices to the latest firmware version (4.5.2-1.0.36229 or later for HMP350/HMP300/DiVA; 4.5.2-1.0.2-1eb2ffbd or later for HMP400/HMP400W/DSOS) to patch the SSRF and Path Traversal vulnerabilities.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15809 — 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-2020-15809 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