CVE-2023-1135
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 Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could set incorrect directory permissions, which could result in local privilege escalation.
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 confidenceIn Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker with local access can set incorrect directory permissions, allowing them to manipulate file system access controls and escalate privileges to higher permission levels (likely administrative or SYSTEM).
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< 1.0.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 if InfraSuite Device Master is installedSearch the system for Delta Electronics InfraSuite Device Master installation directories or check for related services/processes running on the hostAffected if The product is found installed on the system
-
Determine the installed versionLocate the installation directory and find version information in product metadata, about dialog, or version file within the InfraSuite Device Master program filesAffected if The installed version is prior to 1.0.5 (version number is less than 1.0.5)
-
Verify directory permissions on the installation folderInspect file system access control lists (ACLs) on the InfraSuite Device Master installation directory using icacls, Get-Acl, or similar toolsAffected if Directory permissions allow unprivileged users to modify access controls or write to sensitive directories that should be restricted
-
Check for weak permission configurationsReview directory permissions within the InfraSuite installation path for any folders that grant excessive write or modify access to standard users or Everyone groupAffected if Any critical directories have permissions that allow low-privilege users to alter access controls or modify sensitive files
The environment is affected if Delta Electronics InfraSuite Device Master version 1.0.5 or later is not installed, or if directory permissions on the installation folder permit unprivileged users to modify access controls.
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 · scoped1.0.5
Upgrade to Delta Electronics InfraSuite Device Master version 1.0.5 or later, and audit directory permissions on the host to ensure proper restrictive access controls are in place.
1.0.5
- 1. Identify the current version of Infrasuite Device Master installed on the system
- 2. Download Delta Electronics InfraSuite Device Master version 1.0.5 or later from the official vendor source
- 3. Follow the vendor's documented upgrade procedure to apply the update
- 4. After upgrading, verify that directory permissions are correctly set according to vendor hardening guidelines
- 5. Confirm the installed version is 1.0.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1135 — 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-1135 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