CVE-2019-6815
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 · uneditedIn Modicon Quantum all firmware versions, CWE-264: Permissions, Privileges, and Access Control vulnerabilities could cause a denial of service or unauthorized modifications of the PLC configuration when using Ethernet/IP protocol.
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 confidenceThe Modicon Quantum PLC contains a permissions/privilege vulnerability (CWE-264) in its Ethernet/IP protocol implementation. An attacker with network access to the PLC can exploit this to cause denial of service or make unauthorized modifications to the PLC configuration, potentially disrupting industrial processes or altering controller behavior.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm Modicon Quantum PLC modelQuery the PLC hardware or review system inventory documentation to verify the device is a Schneider Electric Modicon Quantum controllerAffected if Device is identified as a Modicon Quantum PLC
-
Identify Ethernet/IP protocol statusReview the PLC network configuration or module list to determine if the Ethernet/IP (ENET) protocol module or stack is enabled on the controllerAffected if Ethernet/IP protocol is configured or enabled on the PLC
-
Assess Ethernet/IP network exposureCheck network topology, firewall rules, or VLAN configuration to determine if the PLC's Ethernet/IP interface is accessible from networks outside the trusted control system segmentAffected if PLC Ethernet/IP port is reachable from untrusted or external networks
-
Inspect for unauthorized configuration changesReview PLC change logs, audit trails, or network monitoring data for unexpected modifications to PLC configuration, program changes, or abnormal Ethernet/IP session activityAffected if Unauthorized or unexpected PLC configuration changes are detected via Ethernet/IP
A Modicon Quantum PLC with Ethernet/IP protocol enabled and accessible from untrusted networks is vulnerable to this CVE
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 dataImplement network segmentation to isolate PLCs from untrusted networks, apply vendor-supplied firmware patches when available, and enforce strict access controls on Ethernet/IP traffic to prevent unauthorized modifications.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6815 — 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-6815 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