CVE-2025-41459
BaseFortify
Publication date: 2025-07-21
Last updated on: 2025-07-22
Assigner: cirosec GmbH
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| two_app_studio | journey | 5.5.7 |
| two_app_studio | journey | 5.5.6 |
| two_app_studio | journey | 5.5.9 |
| two_app_studio | journey | 5.5.8 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the iOS app Two App Studio Journey (versions 5.5.6 to 5.5.9) where the local authentication component does not sufficiently protect against brute-force attacks and runtime manipulation. Local attackers with access to the device's file system can bypass biometric and PIN-based access controls by repeatedly attempting PIN entries or using dynamic code injection, thereby gaining unauthorized access to sensitive data within the app. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access to your private content and key material stored within the app. An attacker with local access to your device could bypass biometric and PIN protections, potentially exposing sensitive personal entries and media. This compromises the confidentiality, integrity, and availability of your data within the app. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability is local to the iOS device and involves the Two App Studio Journey app's local authentication component. Detection involves checking if the device has the vulnerable app version (5.5.6 through 5.5.9) installed and monitoring for repeated PIN attempts or signs of runtime manipulation. Specific commands are not provided in the resources, but you can check the app version via iOS device management tools or by inspecting the app info on the device. Monitoring logs for repeated failed PIN attempts or unusual runtime behavior may help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include enforcing retry limits on PIN attempts, binding authentication to the iOS keychain, and storing sensitive credentials within the Secure Enclave. Since the vendor has not fixed the issue, users should avoid using the vulnerable app versions (5.5.6 through 5.5.9) or restrict local access to the device to trusted users only. Applying any available updates from the vendor once released is also recommended. [1]