Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-2909 Overview
CVE-2025-2909 affects the DuoxMe iOS application (formerly known as Blue) distributed by Fermax in versions prior to 3.3.1. The application binary ships without encryption, allowing an attacker with local access to inspect the compiled code and extract sensitive information embedded within it. The flaw is tracked under CWE-312: Cleartext Storage of Sensitive Information. Spain's INCIBE-CERT published a coordinated advisory covering this and related Fermax mobile application issues.
Critical Impact
An attacker with local access to an iOS device running a vulnerable DuoxMe build can reverse engineer the unencrypted binary and recover sensitive data, including hardcoded secrets and application logic.
Affected Products
- Fermax DuoxMe (formerly Blue) iOS application versions prior to 3.3.1
- iOS devices with the vulnerable DuoxMe build installed
- Fermax Duox intercom ecosystem components reachable through the mobile client
Discovery Timeline
- 2025-03-28 - CVE-2025-2909 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-2909
Vulnerability Analysis
The DuoxMe iOS application binary is distributed without the binary-level encryption protections expected on the platform. Apple's standard App Store distribution typically applies FairPlay encryption to executable segments, which complicates static analysis by third parties. When this protection is absent or stripped, an attacker can load the binary into disassemblers such as Hopper, Ghidra, or IDA Pro and read instructions and string tables directly.
The exposure enables static reverse engineering of application logic, API endpoints, authentication flows, and any embedded secrets. Information recovered from the binary can be used to craft requests against backend services, bypass client-side controls, or construct targeted follow-on attacks against intercom infrastructure.
Root Cause
The root cause is a missing confidentiality control on the application binary itself. CWE-312 describes storage of sensitive information in cleartext, which here extends to code, strings, and symbols left readable within the shipped executable. Developers relied on no additional obfuscation or secrets-at-rest protections, so anyone with filesystem access to the binary can inspect its contents.
Attack Vector
Exploitation requires local access to the iOS device or to a copy of the application binary. An attacker extracts the .ipa package, retrieves the Mach-O executable, and performs static analysis. No user interaction or network privileges are required to recover information from the binary once it has been obtained.
No verified public proof-of-concept code is available. See the INCIBE Security Notice on Vulnerabilities for the coordinated advisory covering the affected Fermax mobile applications.
Detection Methods for CVE-2025-2909
Indicators of Compromise
- Presence of DuoxMe iOS builds with CFBundleShortVersionString below 3.3.1 on managed devices.
- Unexpected copies of the DuoxMe .ipa or extracted Mach-O binaries on developer workstations or shared storage.
- Backend telemetry showing API calls that reuse hardcoded identifiers or endpoints recovered from static analysis.
Detection Strategies
- Inventory iOS endpoints through mobile device management (MDM) and flag DuoxMe installations below version 3.3.1.
- Inspect application binaries with tools such as otool -l to confirm the LC_ENCRYPTION_INFO cryptid value and detect unencrypted builds.
- Review backend access logs for abnormal client fingerprints or request patterns consistent with a reverse-engineered client.
Monitoring Recommendations
- Correlate authentication anomalies on the Fermax backend with device identifiers running outdated DuoxMe versions.
- Alert on sideloaded or re-signed DuoxMe binaries appearing outside the official App Store distribution channel.
- Track MDM compliance drift for the DuoxMe application to confirm patched versions reach every managed device.
How to Mitigate CVE-2025-2909
Immediate Actions Required
- Upgrade DuoxMe for iOS to version 3.3.1 or later on every managed device.
- Rotate any shared secrets, API keys, or tokens that may have been embedded in prior binaries.
- Restrict installation of DuoxMe to the official App Store distribution to reduce exposure to tampered builds.
Patch Information
Fermax addresses the issue in DuoxMe version 3.3.1. Review the INCIBE Security Notice on Vulnerabilities for the vendor-coordinated remediation details and the full list of related Fermax mobile application CVEs.
Workarounds
- Enforce MDM policies that block the vulnerable DuoxMe versions from enrolling or operating on corporate devices.
- Require device-level protections including passcode, biometric unlock, and full-disk encryption to limit local extraction of the binary.
- Segment Fermax intercom backend services and require server-side authorization checks that do not rely on client-side secrets.
# Verify the encryption status of an extracted iOS binary
# cryptid 1 = encrypted, cryptid 0 = unencrypted
otool -l DuoxMe.app/DuoxMe | grep -A4 LC_ENCRYPTION_INFO
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

