dbcve.org
Izzi ConnectApplication · Inprax

CVE-2024-0390

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-15
Fix available
A fix is available. Upgrade to 2024010401 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
INPRAX "iZZi connect" application on Android contains hard-coded MQTT queue credentials. The same MQTT queue is used by corresponding physical recuperation devices. Exploiting this vulnerability could potentially allow unauthorized access to manage and read parameters of the recuperation unit "reQnet iZZi".This issue affects "iZZi connect" application versions before 2024010401.

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 confidence

The iZZi connect Android application contains hard-coded MQTT queue credentials embedded in the app binary. These same credentials are used by physical reQnet iZZi recuperation devices to communicate with a shared MQTT message broker. An attacker who extracts these credentials from the application can connect to the MQTT queue and potentially send management commands or read sensitive parameters from connected physical recuperation devices.

MitigationUpdate the iZZi connect application to version 2024010401 or later, which should remove the hard-coded credentials. Organizations should also rotate the exposed MQTT credentials on the broker side and verify that no unauthorized access has occurred.

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
Izzi ConnectApplication
Affected:< 2024010401

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
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 checks

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

  1. Identify installed iZZi Connect app
    On Android devices, open Settings > Apps > iZZi connect, or use ADB command: 'adb shell pm list packages | grep izzi' to find the package. Check if the app is present on any managed Android devices.
    Affected if The iZZi Connect app by Inprax is installed on any device in the environment.
  2. Determine installed app version
    In Android Settings > Apps > iZZi connect > App info, note the version number shown (which may display as a date code like 2023121501). Alternatively, use ADB: 'adb shell dumpsys package com.inprax.izzi | grep versionName'.
    Affected if A version is found that is earlier than 2024010401.
  3. Compare against affected version range
    Compare the installed version code to the affected range: versions prior to 2024010401 are vulnerable. The vulnerable versions contain hard-coded MQTT credentials embedded in the app binary.
    Affected if The installed version code is less than 2024010401.
  4. Identify exposure to MQTT broker
    If the vulnerable app version is present, determine whether the associated physical iZZi recuperation devices are in use on the network, as these devices communicate with the same MQTT broker using the shared credentials.
    Affected if Physical iZZi recuperation devices are connected to a network-accessible MQTT broker.

If the iZZi Connect Android app version below 2024010401 is installed on any device, the hard-coded MQTT credentials are present in that environment and could be extracted by an attacker to access connected recuperation devices.

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 2024010401 or later
Fixed in 2024010401
Interim mitigation

Update the iZZi connect application to version 2024010401 or later, which should remove the hard-coded credentials. Organizations should also rotate the exposed MQTT credentials on the broker side and verify that no unauthorized access has occurred.

Recommended fix High confidence

2024010401

  1. Check the current version of the Izzi Connect application on your Android device (Settings > Apps > Izzi Connect)
  2. Update the Izzi Connect application to version 2024010401 or later through the Google Play Store or the vendor's official distribution channel
  3. After updating, verify the installation was successful by confirming the new version number in the app settings
  4. As a security best practice following a credentials exposure, consider contacting the device vendor to rotation of the exposed MQTT credentials to ensure the physical recuperation devices use unique, non-compromised credentials

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

Fix this in Izzi Connect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0390 — 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-0390 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