dbcve.org
Ccu3 FirmwareOperating system · Eq 3

CVE-2019-10119

CRITICAL · 9.8 CVSS v3.0 Published 2019-07-10
Fix available
A fix is available. Upgrade to 2.41.8 / 3.43.16 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
eQ-3 HomeMatic CCU2 devices before 2.41.8 and CCU3 devices before 3.43.16 use session IDs for authentication but lack authorization checks. An attacker can obtain a session ID via an invalid login attempt to the RemoteApi account, aka HMCCU-154. This leads to automatic login as admin.

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 HomeMatic CCU2 and CCU3 central control units use session IDs for authentication but fail to perform proper authorization checks. An attacker can obtain a valid admin session ID by making an invalid login attempt to the RemoteApi, bypassing authentication entirely and gaining administrative access to the device.

MitigationUpgrade HomeMatic CCU2 firmware to version 2.41.8 or later, and CCU3 firmware to version 3.43.16 or later to address the missing authorization check.

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
Ccu3 FirmwareOperating system
Affected:< 3.43.16
Ccu2 FirmwareOperating system
Affected:< 2.41.8

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

CVSS:3.0/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 checks

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

  1. Identify the HomeMatic device model
    Access the device web interface or check device documentation to confirm whether it is a CCU2 or CCU3 unit
    Affected if The device is a HomeMatic CCU2 or CCU3 central control unit
  2. Determine the installed firmware version
    Log into the device web interface and navigate to the system settings or status page to view the current firmware version. Alternatively, check the device configuration interface for version information
    Affected if The firmware version is below 2.41.8 on CCU2 or below 3.43.16 on CCU3
  3. Verify RemoteApi accessibility
    Check if the RemoteApi interface is exposed on the network by attempting to access it via the device IP address on typical ports used for RemoteApi (such as port 2001 or 2010)
    Affected if RemoteApi is accessible from the network and accepts requests
  4. Review session management configuration
    Check the device configuration files or settings related to session management and authentication to see if authorization checks are enforced on existing sessions
    Affected if Sessions are created without proper authorization validation after failed login attempts

A user is affected if they are running a HomeMatic CCU2 firmware below 2.41.8 or CCU3 firmware below 3.43.16 with RemoteApi accessible on the network.

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 2.41.8 / 3.43.16 or later
Fixed in 2.41.83.43.16
Interim mitigation

Upgrade HomeMatic CCU2 firmware to version 2.41.8 or later, and CCU3 firmware to version 3.43.16 or later to address the missing authorization check.

Recommended fix High confidence

CCU2: Firmware 2.41.8 or later; CCU3: Firmware 3.43.16 or later

  1. 1. Identify your device model (CCU2 or CCU3) by checking the device label or web interface
  2. 2. Access the CCU web interface and navigate to the system settings to check the current firmware version
  3. 3. Download the firmware update from the official eQ-3 download area at www.eq-3.de - ensure you download version 2.41.8 or later for CCU2, or version 3.43.16 or later for CCU3
  4. 4. In the CCU web interface, go to 'Settings' > 'System Control' > 'Software' or 'Firmware Update'
  5. 5. Upload and install the downloaded firmware file
  6. 6. After the update completes and the device reboots, verify the new firmware version is installed
  7. 7. Test that the RemoteApi authentication now properly validates credentials before granting session access

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

Fix this in Ccu3 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,740
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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