CVE-2018-7299
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 · uneditedRemote Code Execution in the addon installation process in eQ-3 AG Homematic CCU2 2.29.2 and earlier allows authenticated attackers to create or overwrite arbitrary files or install malicious software on the device.
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 confidenceAuthenticated RCE vulnerability in the addon installation process of eQ-3 AG Homematic CCU2 firmware 2.29.2 and earlier allows attackers to create or overwrite arbitrary files on the device, leading to remote code execution or installation of malicious software. The vulnerability likely stems from insufficient validation of file paths or names during the addon upload/installation workflow.
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<= 2.29.22CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:L/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 CCU2 web interface and navigate to the status or system information page, or check the device label/documentation to confirm it is an eQ-3 Homematic CCU2Affected if The device is a Homematic CCU2
-
Check the firmware versionIn the CCU2 web interface, go to Status > Control > Device Information, or access /api/info/version endpoint if available, to determine the installed firmware versionAffected if The firmware version is 2.29.22 or earlier, or cannot be determined to be newer than 2.29.2
-
Determine if the web interface is network-accessibleCheck network configuration to see if the CCU2 web interface (port 80/443) is exposed to untrusted networks or the internet, or verify firewall rules allowing remote accessAffected if The CCU2 web interface is accessible from untrusted networks (not just trusted local LAN)
-
Check if addon installation is enabledIn the CCU2 web interface, navigate to Settings > Addon Settings or examine the configuration file /usr/local/etc/config/ids for addon-related settings to see if addon installation is permittedAffected if Addon installation feature is enabled and accessible to authenticated users
A user is affected if they have a Homematic CCU2 device running firmware version 2.29.22 or earlier, with the web interface accessible to the attacker and the addon installation feature enabled.
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 dataUpdate Homematic CCU2 to firmware version newer than 2.29.2. If immediate patching is not possible, restrict network access to the CCU2 web interface and disable the addon installation feature until the update can be applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7299 — 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-2018-7299 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