Skip to content
Fencer Vulns
high 8.4

CVE-2024-45273 json

MB connect line/Helmholz: Weak encryption of configuration file

published 2024-10-15 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-41406

cvss
8.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits
0
none known

Summary

An unauthenticated local attacker can decrypt the devices config file and therefore compromise the device due to a weak implementation of the encryption used.

Patch / fix

  • helmholz myrex24_v2_virtual_server 2.16.3
  • mbconnectline mbconnect24 2.16.3
  • mbconnectline mymbconnect24 2.16.3
  • mbconnectline mbnet.mini_firmware 2.3.1
  • helmholz rex_200_firmware 8.2.1
  • helmholz rex_250_firmware 8.2.1
  • helmholz rex_100_firmware 2.3.1
  • mbconnectline mbnet_firmware 8.2.1
  • mbconnectline mbnet.rokey_firmware 8.2.1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.09% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • MB connect line mbNET.mini
  • MB connect line mbNET/mbNET.rokey
  • MB connect line mbNET HW1
  • MB connect line mbSPIDER
  • MB connect line mbCONNECT24
  • MB connect line mymbCONNECT24
  • Helmholz REX100
  • Helmholz REX200/250
  • Helmholz myREX24 V2
  • Helmholz myREX24.virtual
  • Helmholz REX300
  • mb_connect_line mbnet.mini
  • mbconnectline mbnet_mbnet.rokey
  • mbconnectline mbnet_hw1
  • mbconnectline mbspider
  • mbconnectline mbconnect24
  • mbconnectline mymbconnect24
  • helmholz rex_200
  • helmholz rex250
  • helmholz myrex24_v2

Classification

Weakness
  • CWE-261 Weak Encoding for Password
  • CWE-326 Inadequate Encryption Strength

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.