CVE-2024-47902
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 · uneditedA vulnerability has been identified in InterMesh 7177 Hybrid 2.0 Subscriber (All versions < V8.2.12), InterMesh 7707 Fire Subscriber (All versions < V7.2.12 only if the IP interface is enabled (which is not the default configuration)). The web server of affected devices does not authenticate GET requests that execute specific commands (such as `ping`) on operating system level.
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 confidenceThis is an unauthenticated command injection vulnerability in the web server of InterMesh 7177 Hybrid 2.0 Subscriber (versions < V8.2.12) and 7707 Fire Subscriber (versions < V7.2.12 with IP interface enabled). Attackers can send unauthenticated GET requests that execute OS-level commands such as ping directly on the device without any authentication.
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< 8.2.12< 7.2.12CVSS 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.1/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 InterMesh device modelAccess the device web interface or check the physical device label. Look for the model number 7177 Hybrid 2.0 Subscriber or 7707 Fire Subscriber.Affected if The device is a Siemens Intermesh 7177 Hybrid 2.0 Subscriber or 7707 Fire Subscriber.
-
Check the installed firmware versionLog into the device web interface and navigate to the Status or System Information page to view the firmware version. Alternatively, check via CLI if available.Affected if The firmware version is below 8.2.12 for the 7177 Hybrid 2.0, or below 7.2.12 for the 7707 Fire Subscriber.
-
For 7707 Fire: verify if IP interface is enabledIn the device web interface, go to Network or Interface settings and check whether the IP interface is turned on. This is not enabled by default.Affected if The device is a 7707 Fire Subscriber with IP interface enabled, and firmware is below 7.2.12.
-
Confirm web server is network accessibleCheck if the device web server (HTTP/HTTPS on port 80/443 or custom ports) is reachable from network segments accessible to potential attackers.Affected if The web interface is exposed to untrusted networks without firewall restrictions.
You are affected if you have an InterMesh 7177 Hybrid 2.0 Subscriber with firmware below 8.2.12, or a 7707 Fire Subscriber with firmware below 7.2.12 and the IP interface 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.
dbcve · scoped7.2.128.2.12
Upgrade InterMesh 7177 Hybrid devices to V8.2.12 or later, and 7707 Fire devices to V7.2.12 or later. For 7707 Fire devices, keep the IP interface disabled unless explicitly required, as it is not enabled by default.
Intermesh 7177 Hybrid 2.0 Subscriber: upgrade to V8.2.12 | Intermesh 7707 Fire Subscriber: upgrade to V7.2.12
- 1. Identify the specific Intermesh device model (7177 Hybrid 2.0 Subscriber or 7707 Fire Subscriber)
- 2. Check the current firmware version of the device
- 3. For Intermesh 7707 Fire Subscriber: Verify whether the IP interface is enabled (if disabled, this vulnerability does not apply as it is not the default configuration)
- 4. Obtain the firmware upgrade from official Siemens/cert-portal sources: V8.2.12 for 7177 Hybrid 2.0 Subscriber, V7.2.12 for 7707 Fire Subscriber
- 5. Apply the firmware upgrade following the vendor's documented upgrade procedure
- 6. After upgrade, verify the web server now properly authenticates GET requests before executing OS-level commands
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47902 — 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-2024-47902 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