Skip to main content
VulnerabilityPublished Updated

CVE-2024-45274: MB connect line mbNET.mini · Missing Authentication

Affects MB connect line mbNET.miniSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.5% chance of exploitation in 30 days – higher than 74% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
MB connect line mbNET.miniAffected
  • =0.0.0
Fixed in–

AI-suggested

1. Immediately restrict UDP traffic to and from mbNET.mini devices using network segmentation and firewall rules to limit exposure to untrusted networks. 2. Disable UDP services on the device if not required for operational purposes. 3. Implement strict network access controls, allowing only trusted management stations to communicate with the device. 4. Monitor network traffic for unusual UDP packets targeting mbNET.mini devices, employing intrusion detection systems with custom signatures if possible. 5. Engage with MB connect line vendor support channels to obtain patches or firmware updates as soon as they become available. 6. Conduct thorough audits of all mbNET.mini deployments to identify exposed devices and assess risk. 7. Consider deploying compensating controls such as VPNs or secure tunnels for device management to add authentication layers. 8. Train operational technology (OT) and IT security teams on this vulnerability to ensure rapid response and remediation. 9. Maintain up-to-date asset inventories to quickly identify affected devices during incident response. 10. Review and enhance overall OT network security posture to reduce the risk of similar vulnerabilities.

Description

An unauthenticated remote attacker can execute OS commands via UDP on the device due to missing authentication.

References

Community reviews

Loading reviews…