# CVE-2025-2909: Lack of encryption vulnerability in DuoxMe

> An attacker can access sensitive information by exploiting the lack of encryption in the DuoxMe iOS application binary.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 28 Mar 2025
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-hfvj-w63f-mc9j

## What is CVE-2025-2909?

CVE-2025-2909 is a medium-severity vulnerability in Fermax DuoxMe iOS application, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The lack of encryption in the DuoxMe (formerly Blue) application binary in versions prior to 3.3.1 for iOS devices allows an attacker to gain unauthorised access to the application code and discover sensitive information.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2025-2909?


## How do I fix CVE-2025-2909?

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

## Is CVE-2025-2909 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2909 and fix it if it is affected.

What it is: CVE-2025-2909 is a medium-severity vulnerability in Fermax DuoxMe iOS application, published on 28 Mar 2025. 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-2025-2909 in the wild and no public exploit code.

Affected product: Fermax DuoxMe iOS 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-2025-2909/ (Markdown: https://insights.sbomify.com/CVE-2025-2909/index.md)
```

## Sources

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

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