dbcve.org
Mbnet.mini FirmwareOperating system · Mbconnectline

CVE-2024-45273

HIGH · 7.8 CVSS v3.1 Published 2024-10-15
Fix available
A fix is available. Upgrade to 2.3.1 / 2.16.3 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
An unauthenticated local attacker can decrypt the devices config file and therefore compromise the device due to a weak implementation of the encryption used.

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 · moderate confidence

The vulnerability allows an unauthenticated local attacker to decrypt the device's configuration file due to a weak encryption implementation. This exposes sensitive credentials and settings embedded in the config, enabling full device compromise.

MitigationReplace the weak encryption with a strong, standard cryptographic algorithm (e.g., AES-256-GCM) with proper key management. Ensure config files are encrypted at rest using securely generated keys and consider adding authentication to prevent unauthorized access to decryption operations.

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
Mbnet.mini FirmwareOperating system
Affected:< 2.3.1
Myrex24 V2 Virtual ServerApplication
Affected:< 2.16.3
Rex 300 FirmwareOperating system
Affected:<= 5.1.11
Rex 200 FirmwareOperating system
Affected:< 8.2.1
Rex 250 FirmwareOperating system
Affected:< 8.2.1
Rex 100 FirmwareOperating system
Affected:< 2.3.1
Mbconnect24Application
Affected:< 2.16.3
Mymbconnect24Application
Affected:< 2.16.3

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify product and model
    Locate the device or software name on the physical device label, web interface, or system information (e.g., Mbnet.mini, Myrex24 V2 Virtual Server, Rex 300, Rex 200, Rex 250, Rex 100, Mbconnect24, Mymbconnect24)
    Affected if The product is one of the eight affected products listed in the CVE
  2. Check installed firmware or software version
    Access the device web interface, admin panel, or CLI and locate the firmware/software version information (often in About, System Info, or Status sections)
    Affected if Version is lower than the affected threshold: Mbnet.mini < 2.3.1, Myrex24 V2 < 2.16.3, Rex 300 <= 5.1.11, Rex 200 < 8.2.1, Rex 250 < 8.2.1, Rex 100 < 2.3.1, Mbconnect24 < 2.16.3, Mymbconnect24 < 2.16.3
  3. Locate the configuration file
    Find the device configuration file on the device filesystem, backup storage, or exported config archive (commonly named config.dat, config.bin, settings.bin, or similar encrypted config file)
    Affected if A configuration file exists and is stored on the device or in backups
  4. Test for weak encryption decryption
    Attempt to decrypt the config file using weak or known insecure encryption methods (such as hardcoded keys, simple XOR, DES, or ECB-mode block ciphers with default keys). If plaintext credentials, passwords, or settings become readable, weak encryption is confirmed.
    Affected if The config file decrypts successfully using weak encryption methods, exposing sensitive credentials or settings in plaintext

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.3.1 / 2.16.3 / 8.2.1 or later
Fixed in 2.3.12.16.38.2.1
Interim mitigation

Replace the weak encryption with a strong, standard cryptographic algorithm (e.g., AES-256-GCM) with proper key management. Ensure config files are encrypted at rest using securely generated keys and consider adding authentication to prevent unauthorized access to decryption operations.

Recommended fix Moderate confidence

Upgrade to firmware version 2.3.1 for Mbnet.mini/Rex 100; version 2.16.3 for Myrex24 V2 Virtual Server/Mbconnect24/Mymbconnect24; version 8.2.1 for Rex 200/Rex 250; version >5.1.11 for Rex 300

  1. 1. Identify the specific Mbnet or Rex device model from the affected product list
  2. 2. Determine the current firmware version of the device
  3. 3. Download the corresponding fixed firmware version from the vendor's official support site: Mbnet.mini upgrade to 2.3.1 or later, Myrex24 V2 Virtual Server upgrade to 2.16.3 or later, Rex 300 upgrade to a version higher than 5.1.11, Rex 200 upgrade to 8.2.1 or later, Rex 250 upgrade to 8.2.1 or later, Rex 100 upgrade to 2.3.1 or later, Mbconnect24 upgrade to 2.16.3 or later, Mymbconnect24 upgrad
  4. 4. Review vendor release notes to confirm the security fix for CVE-2024-45273 is included
  5. 5. Backup current device configuration before upgrading
  6. 6. Follow vendor's documented firmware upgrade procedure for your specific device
  7. 7. After upgrade, verify the device is functioning correctly and the configuration file uses the updated encryption mechanism
Caveat Review vendor release notes for potential configuration changes or feature modifications between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mbnet.mini Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45273 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45273 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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