dbcve.org
Aladdin ConnectApplication · Geniecompany

CVE-2023-5879

MEDIUM · 6.8 CVSS v3.1 Published 2024-01-03
Fix available
A fix is available. Upgrade to 5.73 or later.
See remediation →
73/100
Remediation priority · Elevated
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
Users’ product account authentication data was stored in clear text in The Genie Company Aladdin Connect Mobile Application Version 5.65 Build 2075 (and below) on Android Devices. This allows the attacker, with access to the android device, to potentially retrieve users' clear text authentication credentials.

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 Aladdin Connect Mobile Application for Android (version 5.65 Build 2075 and below) stores user authentication credentials in plaintext within local device storage. Any attacker with physical access or root privileges to the device can retrieve these unencrypted credentials.

MitigationThe application should be updated to use Android's secure storage mechanisms (Keystore system, EncryptedSharedPreferences, or similar) to encrypt sensitive authentication data at rest rather than storing it in plaintext.

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
Aladdin ConnectApplication
Affected:< 5.73

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

CVSS:3.1/AV:P/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. Verify Aladdin Connect app is installed
    Go to Settings > Apps on the Android device and locate 'Aladdin Connect' in the app list. Note the installed version number displayed.
    Affected if The app is installed and version shown is below 5.73 (for example, 5.65, 5.60, etc.)
  2. Check app version in package manager
    Run 'adb shell dumpsys package com.geniecompany.aladdinconnect' or use a file manager app to access /data/data/ and locate the app's manifest or package info showing versionName.
    Affected if VersionName field shows a version less than 5.73
  3. Inspect SharedPreferences for plaintext credentials
    Using a root file explorer or ADB, navigate to /data/data/com.geniecompany.aladdinconnect/shared_prefs/ and open XML preference files. Look for fields that may contain username, password, token, or auth credentials in plaintext.
    Affected if Any XML file contains unencrypted username, password, token, authToken, or similar credential-like strings in plain text format
  4. Check internal storage for credential files
    Navigate to /data/data/com.geniecompany.aladdinconnect/files/ and /data/data/com.geniecompany.aladdinconnect/databases/ using root access. Search for any files that may store user authentication data without encryption.
    Affected if Database or file storage contains plaintext authentication credentials

The device is affected if Aladdin Connect Android app version is below 5.73 AND plaintext authentication credentials are found in local app storage.

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

The application should be updated to use Android's secure storage mechanisms (Keystore system, EncryptedSharedPreferences, or similar) to encrypt sensitive authentication data at rest rather than storing it in plaintext.

Recommended fix High confidence

Version 5.73 or later

  1. 1. Open the Google Play Store on the Android device
  2. 2. Search for "Aladdin Connect" or "Genie Aladdin Connect"
  3. 3. If an update is available, tap "Update" to install version 5.73 or later
  4. 4. Alternatively, enable automatic app updates in Google Play Store settings to ensure future security updates are applied
  5. 5. After updating, verify the app version in Settings > Apps > Aladdin Connect > Version to confirm version 5.73 or higher is installed

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

Fix this in Aladdin Connect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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