CVE-2024-27768
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 · uneditedUnitronics Unistream Unilogic – Versions prior to 1.35.227 - CWE-22: 'Path Traversal' may allow RCE
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 path traversal vulnerability (CWE-22) in Unitronics Unistream Unilogic versions prior to 1.35.227 allows attackers to manipulate file path inputs to traverse directories and potentially write or execute arbitrary code, leading to full remote compromise of the device.
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.35.227CVSS 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 Unitronics Unistream with Unilogic in your environmentLocate any Unitronics Unistream PLCs or HMIs running Unilogic software. Check your asset inventory or scan the network for Unitronics devices.Affected if Unistream device running Unilogic is present
-
Determine installed Unilogic versionAccess the Unilogic software or device web interface and locate the version information, typically found in Help > About or the runtime system settings.Affected if Version is shown as lower than 1.35.227
-
Check if remote/network access is enabledVerify whether the Unilogic web server, remote access, or network communication features are enabled on the device. This is typically configured in the Unilogic project settings under Communications or Network.Affected if Remote or web access is enabled and Unilogic version is below 1.35.227
-
Inspect web request logs for path traversal patternsReview server or device logs for suspicious requests containing ../ patterns, such as ../../../etc/passwd or similar directory traversal sequences in HTTP requests.Affected if Such patterns are found in logs and Unilogic version is below 1.35.227
You are affected if a Unitronics Unistream device running Unilogic with remote/network access enabled has a version lower than 1.35.227.
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 data1.35.227
Upgrade Unilogic to version 1.35.227 or later. If immediate patching is not feasible, implement network segmentation to restrict unauthorized access and deploy WAF rules to detect and block path traversal patterns in HTTP requests.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27768 — 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-2024-27768 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