# CVE-2023-5879: Aladdin Connect Android Application Insecure Storage

> Attackers with device access can retrieve clear-text authentication credentials from the Aladdin Connect Android application, potentially leading to account takeover.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-cj4v-24xq-mcm6

## What is CVE-2023-5879?

CVE-2023-5879 is a medium-severity vulnerability in The Genie Company Aladdin Connect Mobile Application, published on 3 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2023-5879?

It affects 1 product.


Products: Geniecompany Aladdin Connect.

## How do I fix CVE-2023-5879?

No fix has been published for CVE-2023-5879 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-5879 being exploited?

There is no known exploitation of CVE-2023-5879 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5879 and fix it if it is affected.

What it is: CVE-2023-5879 is a medium-severity vulnerability in The Genie Company Aladdin Connect Mobile Application, published on 3 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5879 in the wild and no public exploit code.

Affected product: The Genie Company Aladdin Connect Mobile Application. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5879/ (Markdown: https://insights.sbomify.com/CVE-2023-5879/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5879
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5879
- OSV: https://osv.dev/vulnerability/CVE-2023-5879

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5879/
Summaries are generated and may contain mistakes; the official description above is the record.