CVE-2019-6814
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 · uneditedA CWE-287: Improper Authentication vulnerability exists in the NET55XX Encoder with firmware prior to version 2.1.9.7 which could cause impact to confidentiality, integrity, and availability when a remote attacker crafts a malicious request to the encoder webUI.
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 confidenceA CWE-287 Improper Authentication vulnerability in the NET55XX Encoder webUI allows remote attackers to bypass authentication mechanisms with malicious requests. This affects devices running firmware versions prior to 2.1.9.7, potentially giving attackers unauthorized access to compromise confidentiality, integrity, and availability.
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< 2.1.9.7< 2.1.9.7< 2.1.9.7< 2.1.9.7< 2.1.9.7< 2.1.9.7< 2.1.9.7CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 the NET55XX encoder modelLocate the device label or access the webUI system information page to confirm the exact model (Net5500, Net5501, Net5501 I, Net5501 Xt, Net5504, Net5508, or Net5516).Affected if The device is any NET55XX encoder model.
-
Determine the installed firmware versionAccess the webUI admin interface and navigate to System Information or Firmware/Upgrade settings to view the currently installed firmware version. Alternatively, check the device label or documentation for firmware version sticker.Affected if The installed firmware version cannot be determined or is visible.
-
Compare firmware version against the affected rangeCompare the installed firmware version number to 2.1.9.7. The vulnerability affects all versions prior to 2.1.9.7.Affected if The installed firmware version is below 2.1.9.7.
-
Confirm webUI is accessibleVerify that the device web interface is reachable on the network by attempting to access the device IP on ports 80 or 443, or by checking network listening services on the device.Affected if The webUI is exposed and accessible on the network.
The environment is affected if the NET55XX encoder device is running firmware version lower than 2.1.9.7 and the webUI 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.
dbcve · scoped2.1.9.7
Update NET55XX Encoder firmware to version 2.1.9.7 or later to remediate the improper authentication vulnerability.
Firmware version 2.1.9.7
- Identify the exact Net55XX model (Net5501, Net5501 I, Net5501 Xt, Net5504, Net5500, Net5516, or Net5508) currently deployed
- Access the encoder webUI or management interface
- Navigate to the firmware upgrade section
- Download the firmware version 2.1.9.7 or later from the official Schneider Electric website (www.se.com)
- Upload and apply the firmware version 2.1.9.7 to the encoder device
- Verify the upgrade was successful by checking the firmware version in the device management interface
- Confirm the webUI is accessible and the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6814 — 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-6814 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