Use of Shared Cryptographic Key in mH-DEVELOPER
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| F&F Filipowski | mH-DEVELOPER | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| F&f Filipowski | Mh-developer |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.238% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
F&f Filipowski
F&f Filipowski mh-developer |
|
| Vendors & Products |
F&f Filipowski
F&f Filipowski mh-developer |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | mH-DEVELOPER smart home module uses the same hard-coded SSH host keys on every device, with no per-device key generation. An attacker who extracts these keys from the firmware can set up a rogue SSH server that clients will trust without warning, enabling man-in-the-middle attacks and credential interception. This issue was fixed in version 3.0.30 | |
| Title | Use of Shared Cryptographic Key in mH-DEVELOPER | |
| First Time appeared |
F F Filipowski
F F Filipowski mh-developer |
|
| Weaknesses | CWE-321 | |
| CPEs | cpe:2.3:a:f_f_filipowski:mh-developer:*:*:*:*:*:*:*:* | |
| Vendors & Products |
F F Filipowski
F F Filipowski mh-developer |
|
| References |
| |
| Metrics |
cvssV4_0
|