dbcve.org
UnilogicApplication · Unitronics

CVE-2024-27774

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 1.35.227 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Unitronics Unistream Unilogic – Versions prior to 1.35.227 - CWE-259: Use of Hard-coded Password may allow disclosing Sensitive Information Embedded inside Device's Firmware

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 confidence

Unitronics Unistream PLC controllers contain a hardcoded password embedded in the device firmware (CWE-259). This vulnerability may allow an authenticated attacker to access sensitive information by using the hardcoded credentials. The issue affects Unilogic versions prior to 1.35.227.

MitigationUpdate Unitronics Unistream devices to firmware version 1.35.227 or later to remove the hardcoded password. Prior to updating, inventory all affected devices, create backups, and schedule maintenance windows to minimize operational disruption.

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
UnilogicApplication
Affected:< 1.35.227

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is a Unitronics Unistream PLC
    Identify the PLC model on the device hardware label, or via the UniLogic software by connecting to the controller and viewing the controller properties. Look for 'Unistream' in the model designation.
    Affected if The device is a Unitronics Unistream PLC controller - other Unitronics series are not affected by this specific CVE.
  2. Check the installed Unilogic software version
    In UniLogic, go to the Help menu and select 'About UniLogic' to view the exact version number. Alternatively, when connected to the controller, the version may be displayed in the controller information or system status screen.
    Affected if The installed version is earlier than 1.35.227 - versions prior to this contain the hardcoded password.
  3. Determine if PLC programming or remote access is enabled
    Review the PLC network configuration settings in UniLogic under 'Communication' or 'Network Settings'. Check if remote access, remote programming, or VNC access features are enabled. Also verify what authentication methods are configured for accessing the controller.
    Affected if Remote or network-based authenticated access to the controller is enabled, as the hardcoded password would only be useful for an authenticated attacker.
  4. Identify if the hardcoded credential could be used
    Check if default or factory authentication credentials are still in use, or if custom passwords have been applied to user accounts. Review any service accounts or shared credentials that may exist in the PLC user management configuration.
    Affected if Default credentials remain unchanged or the hardcoded password matches an active account on the controller.

You are affected if you have a Unitronics Unistream PLC with UniLogic software version earlier than 1.35.227, and the controller has authenticated network or remote access enabled that could utilize the hardcoded password.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.35.227 or later
Fixed in 1.35.227
Interim mitigation

Update Unitronics Unistream devices to firmware version 1.35.227 or later to remove the hardcoded password. Prior to updating, inventory all affected devices, create backups, and schedule maintenance windows to minimize operational disruption.

Recommended fix Moderate confidence

1.35.227

  1. 1. Identify the current Unilogic version installed on the Unitronics Unistream PLC.
  2. 2. Download Unilogic version 1.35.227 or later from the official Unitronics website or trusted distribution channel.
  3. 3. Create a backup of the current project files and PLC configuration before proceeding with the upgrade.
  4. 4. Disconnect the PLC from any production networks or ensure proper network isolation.
  5. 5. Install the Unilogic upgrade following the vendor's standard installation procedure.
  6. 6. After installation, verify the new version is 1.35.227 or higher.
  7. 7. Reconnect to the PLC and verify normal operation.
Caveat No specific breaking changes documented in the provided sources; standard upgrade precautions apply

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unilogic Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-27774 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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