CVE-2019-6542
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 · uneditedENTTEC Datagate MK2, Storm 24, Pixelator all firmware versions prior to (70044,70050,70060)_update_05032019-482 allows an unauthenticated user to initiate a remote reboot, which may be used to cause a denial of service condition.
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 confidenceENTTEC Datagate MK2, Storm 24, and Pixelator DMX lighting control devices running firmware versions prior to (70044,70050,70060)_update_05032019-482 contain an unauthenticated remote reboot vulnerability. An attacker can send unauthenticated requests to trigger device reboots, causing denial of service.
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< 70044_update_05032019-482< 70050_update_05032019-482< 70060_update_05032019-482CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device modelAccess the device web interface or check the device label to determine if it is an Enttec Datagate Mk2, Storm 24, or Pixelator DMX controllerAffected if The device is any of these three models
-
Determine the firmware versionLog into the device web interface and navigate to the Settings or About page to view the installed firmware version numberAffected if The firmware version cannot be verified or is below the patched versions
-
Compare firmware to affected versionsCheck if the installed firmware version is lower than 70044_update_05032019-482 for Datagate Mk2, 70050_update_05032019-482 for Storm 24, or 70060_update_05032019-482 for PixelatorAffected if The installed version is lower than any of these threshold versions
-
Verify network exposure of management interfaceCheck if the device management interface (web UI or API) is accessible from untrusted or external networks, or verify firewall rules allow direct access from outside the local networkAffected if The management interface is exposed to untrusted networks without access controls
A user is affected if they are running any of the three Enttec device models with firmware versions below the patched thresholds AND the device management interface is network-accessible.
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 data70044_update_05032019-48270050_update_05032019-48270060_update_05032019-482
Update firmware to versions 70044, 70050, or 70060 (corresponding to each device model) with the _update_05032019-482 patch. If immediate patching is not possible, consider network segmentation to restrict access to management interfaces.
- Consultation4.0 h
- Implementation6.0 h
- Testing2.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 $4,064.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6542 — 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-2019-6542 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