CVE-2023-1142
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 use URL decoding to retrieve system files, credentials, and bypass authentication resulting in 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 confidenceDelta Electronics InfraSuite Device Master versions prior to 1.0.5 contain a path traversal vulnerability exploitable via URL encoding manipulation. Attackers can decode URL-encoded paths to access sensitive system files, retrieve stored credentials, bypass authentication mechanisms, and escalate privileges to administrative levels.
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
- 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 InfraSuite Device Master installation and versionLocate the InfraSuite Device Master application on the system and determine its installed version number. This may be found in the application itself, in installed programs list, or in version information files within the application directory.Affected if The installed version is lower than 1.0.5 (for example, 1.0.4, 1.0.3, or earlier)
-
Confirm web interface accessibilityVerify that the InfraSuite Device Master web interface is accessible on the network. This vulnerability is exploitable through HTTP requests, so an exposed web service is required for the flaw to be triggered.Affected if The web interface is exposed and accepts HTTP requests from potential attackers
-
Check for URL-encoded path traversal vulnerabilityTest whether the web application properly handles URL-encoded path sequences such as %2e%2e%2f (encoded ../). Submit a request with encoded path traversal sequences to see if the application returns files outside the intended directory.Affected if The application returns file contents or directory listings for paths outside the web root when using URL-encoded traversal sequences
-
Look for unauthorized file access indicatorsReview web server access logs for requests containing encoded path sequences (%2e, %2f, %5c) or unusual path patterns. Check if sensitive files such as configuration files, credential stores, or system files have been accessed unexpectedly.Affected if Logs show successful requests with URL-encoded path traversal sequences or evidence of unauthorized file access
A user is affected if InfraSuite Device Master version is below 1.0.5 AND the web interface is accessible, allowing attackers to exploit URL-encoded path traversal to access sensitive files or bypass authentication.
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 InfraSuite Device Master version 1.0.5 or later. Implement strict input validation on all URL parameters, disable directory listing, and restrict file system access permissions as additional hardening until the patch can be applied.
1.0.5
- 1. Identify all instances of Infrasuite Device Master currently deployed
- 2. Verify the current version of each instance (versions prior to 1.0.5 are vulnerable)
- 3. Obtain the patched version 1.0.5 from the vendor's official distribution channel
- 4. Follow vendor-provided upgrade documentation to apply version 1.0.5
- 5. After upgrade, verify the version has been correctly applied
- 6. Test that the path traversal vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1142 — 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-1142 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