dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2024-35295

MEDIUM · 6.1 CVSS v3.1 Published 2025-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
No privileges 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
A vulnerability has been identified in Perfect Harmony GH180 (All versions >= V8.0 < V8.3.3 with NXGPro+ controller manufactured between April 2020 to April 2025). The maintenance connection of affected devices fails to protect access to the device's control unit configuration. This could allow an attacker with physical access to the maintenance connection's door port to perform arbitrary configuration changes.

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 confidence

The Perfect Harmony GH180 controller (NXGPro+ models manufactured April 2020-April 2025, running firmware V8.0 to V8.3.2) has a vulnerability in the maintenance connection door port. This maintenance port fails to properly protect access to the control unit configuration, allowing a physically proximate attacker to make arbitrary configuration changes.

MitigationUpgrade firmware to V8.3.3 or later and implement physical access controls around the maintenance connection door port to prevent unauthorized local access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/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 checks

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

  1. Identify the controller model
    Locate the physical device or system documentation and confirm it is a Perfect Harmony GH180 controller, specifically the NXGPro+ variant. Check the device label or management interface for the model designation.
    Affected if The device is a Perfect Harmony GH180 NXGPro+ controller
  2. Verify manufacturing date
    Check the manufacturing date on the device label, shipping documentation, or system inventory records. The vulnerability affects units manufactured between April 2020 and April 2025.
    Affected if The manufacturing date falls between April 2020 and April 2025 inclusive
  3. Check installed firmware version
    Access the controller's management interface or firmware information page and identify the current firmware version. Compare against the affected range V8.0 to V8.3.2.
    Affected if The installed firmware version is V8.0, V8.1, V8.2, V8.3, V8.3.1, or V8.3.2
  4. Inspect maintenance connection door port
    Physically examine the controller unit for the maintenance connection door port. Determine whether the port is present and accessible without special tools or authentication. This port provides direct access to control unit configuration.
    Affected if The maintenance connection door port is physically accessible and allows direct access to configuration settings

The environment is affected if it contains a Perfect Harmony GH180 NXGPro+ controller manufactured between April 2020 and April 2025, running firmware V8.0 through V8.3.2, with an accessible maintenance connection door port that permits unrestricted configuration changes.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade firmware to V8.3.3 or later and implement physical access controls around the maintenance connection door port to prevent unauthorized local access.

Recommended fix Moderate confidence

V8.3.3 or later

  1. 1. Identify the current firmware version of the Perfect Harmony GH180 device by accessing the device configuration or control system interface
  2. 2. Verify the device is within the affected range: versions V8.0 through V8.2.x with NXGPro+ controller
  3. 3. Contact Innomotics (or Siemens) technical support to obtain the firmware upgrade package for version V8.3.3 or later
  4. 4. Follow the manufacturer's documented firmware update procedure, ensuring proper physical access controls are maintained during the upgrade process
  5. 5. After upgrading, verify the device is running version V8.3.3 or later and confirm the maintenance connection now properly protects access to the control unit configuration

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35295 — 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-35295 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