CVE-2019-10122
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 · uneditedeQ-3 HomeMatic CCU2 devices before 2.41.9 and CCU3 devices before 3.43.16 have buffer overflows in the ReGa ise GmbH HTTP-Server 2.0 component, aka HMCCU-179. This may lead to remote code execution.
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 confidenceBuffer overflow vulnerabilities in the ReGa ise GmbH HTTP-Server 2.0 component of eQ-3 HomeMatic CCU2 and CCU3 smart home control units allow remote attackers to execute arbitrary code via crafted HTTP requests. The critical severity (CVSS 9.8) stems from the lack of authentication requirements for exploitation and the direct path to remote code execution.
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< 3.43.16< 2.41.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the CCU web interface and check the device information page, or check the physical device label for CCU2 or CCU3 model designationAffected if The device is an eQ-3 HomeMatic CCU2 or CCU3 control unit
-
Determine the installed firmware versionLog into the CCU web interface and navigate to Status and Control > Device Variables, or access /api/info/version via the local HTTP APIAffected if For CCU2: version is below 2.41.9; for CCU3: version is below 3.43.16
-
Verify the ReGa HTTP server is accessibleAttempt to access the HTTP server on the CCU device default ports (80/443) from the networkAffected if The HTTP server component is network-accessible without authentication
A defender is affected if they are running a CCU2 firmware below 2.41.9 or CCU3 firmware below 3.43.16 with the HTTP server exposed on the network.
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 · scoped2.41.93.43.16
Update HomeMatic CCU2 firmware to version 2.41.9 or later and CCU3 firmware to version 3.43.16 or later to address the buffer overflow vulnerabilities in the HTTP server component.
CCU2: firmware >= 2.41.9 | CCU3: firmware >= 3.43.16
- Identify the device model: CCU2 or CCU3
- Download the appropriate firmware update from the official eQ-3 website (www.eq-3.de): CCU2 version 2.41.9 or later, CCU3 version 3.43.16 or later
- Review eQ-3 firmware update instructions to understand the update process
- Back up any critical configuration or data before proceeding with the update
- Apply the firmware update following the vendor's documented procedure
- After updating, verify the device is operational and running the patched firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10122 — 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-2019-10122 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