CVE-2023-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 · uneditedIncorrect Privilege Assignment vulnerability in Mitsubishi Electric Corporation MELSEC iQ-R Series Safety CPU R08/16/32/120SFCPU all versions and MELSEC iQ-R Series SIL2 Process CPU R08/16/32/120PSFCPU all versions allows a remote authenticated attacker who has logged into the product as a non-administrator user to disclose the credentials (user ID and password) of a user with a lower access level than the attacker by sending a specially crafted packet.
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 confidenceIncorrect Privilege Assignment vulnerability in Mitsubishi Electric MELSEC iQ-R Series Safety CPU and SIL2 Process CPU allows an authenticated non-administrator user to send specially crafted packets to disclose credentials (user ID and password) of users with lower access levels. The vulnerability stems from improper authorization checks in the web interface or management interface that should prevent lower-privilege user credential disclosure.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- 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 affected CPU modelLocate the CPU module model number on the MELSEC iQ-R Series Safety CPU or SIL2 Process CPU device labeling or in the engineering software project configuration under CPU module settingsAffected if The model is one of: R08sfcpu, R16sfcpu, R32sfcpu, R120sfcpu, R08psfcpu, R16psfcpu, R32psfcpu, or R120psfcpu
-
Confirm firmware versionAccess the CPU module via GX Works3 engineering software or the device web interface and check the firmware version in the module information or system information screenAffected if Any firmware version is installed since all versions are affected
-
Verify management interface is accessibleCheck if the web-based management interface or HTTP/HTTPS service is enabled and reachable on the device by attempting to access the device IP in a web browser or checking open network portsAffected if The web interface or management interface is enabled and accessible on the network
-
Check for non-administrator user accountsReview user account configuration in the CPU module security settings via GX Works3 or the web interface to confirm multiple user accounts exist with different privilege levelsAffected if More than one user account is configured, or any non-administrator user account exists alongside administrator accounts
-
Inspect for credential disclosure capabilityLog in as a non-administrator user and attempt to access user management or credential listing functions within the web interface or management interfaceAffected if A non-administrator user can view, retrieve, or access user ID or password information for other users
You are affected if you run any of the listed CPU models with the web interface or management interface enabled and have non-administrator user accounts configured on the device.
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 vendor patches if available; otherwise restrict network access to the device management interfaces, implement strong network segmentation, and monitor for unusual authenticated requests. Consider compensating controls like limiting admin account creation and using external authentication if supported.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-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-2023-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