CVE-2025-57197: n/a
In the Payeer Android application 2.5.0, an improper access control vulnerability exists in the authentication flow for the PIN change feature. A local attacker with root access to the device can dynamically instrument the app to bypass the current PIN verification check and directly modify the authentication PIN. This allows unauthorized users to change PIN without knowing the original/current PIN.
AI Analysis
Technical Summary
CVE-2025-57197 identifies a security vulnerability in the Payeer Android application version 2.5.0 related to improper access control in the PIN change authentication flow. Specifically, the vulnerability allows a local attacker who has obtained root access on the Android device to bypass the PIN verification step during the PIN change process. By dynamically instrumenting the application—modifying its runtime behavior—the attacker can circumvent the check that normally requires the current PIN to authorize a PIN change. This flaw stems from inadequate enforcement of access control (CWE-284) within the authentication logic, permitting unauthorized modification of the authentication PIN without knowledge of the original PIN. The vulnerability does not require user interaction but does require elevated privileges (root access) on the device, which limits the attack surface to already compromised devices. The CVSS v3.1 base score is 6.0, reflecting medium severity with high impact on confidentiality and integrity but no impact on availability. No known exploits are reported in the wild, and no patches have been linked yet. This vulnerability could allow attackers to take over user accounts by changing authentication credentials, potentially leading to unauthorized financial transactions or data exposure within the Payeer platform.
Potential Impact
For European organizations, especially those in the financial sector or those relying on Payeer for payment processing or wallet services, this vulnerability poses a significant risk to user account security. If an attacker gains root access to a device, they can bypass PIN protections and change authentication credentials, leading to unauthorized access to funds or sensitive financial data. This undermines user trust and could result in financial losses, regulatory penalties under GDPR for data breaches, and reputational damage. The impact is heightened in environments where devices are more likely to be rooted or compromised, such as among tech-savvy users or in organizations with lax device security policies. Since the vulnerability requires local root access, the threat is more relevant in scenarios involving insider threats, lost or stolen devices, or malware that escalates privileges. European organizations with mobile workforces or BYOD policies should be particularly cautious.
Mitigation Recommendations
1. Restrict and monitor root access on Android devices used within the organization to prevent attackers from gaining the necessary privileges to exploit this vulnerability. 2. Implement mobile device management (MDM) solutions that detect and block rooted or jailbroken devices from accessing corporate resources or sensitive applications like Payeer. 3. Employ runtime application self-protection (RASP) or integrity verification mechanisms within the Payeer app to detect and prevent dynamic instrumentation or tampering attempts. 4. Educate users about the risks of rooting devices and encourage use of official, unmodified app versions only. 5. Monitor for unusual PIN change activities or authentication anomalies within Payeer accounts to detect potential exploitation. 6. Coordinate with Payeer to obtain and apply security patches promptly once available. 7. Enforce multi-factor authentication (MFA) where possible to add an additional security layer beyond PIN protection. 8. Regularly audit and update device security policies to minimize the risk of privilege escalation on mobile devices.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain
CVE-2025-57197: n/a
Description
In the Payeer Android application 2.5.0, an improper access control vulnerability exists in the authentication flow for the PIN change feature. A local attacker with root access to the device can dynamically instrument the app to bypass the current PIN verification check and directly modify the authentication PIN. This allows unauthorized users to change PIN without knowing the original/current PIN.
AI-Powered Analysis
Technical Analysis
CVE-2025-57197 identifies a security vulnerability in the Payeer Android application version 2.5.0 related to improper access control in the PIN change authentication flow. Specifically, the vulnerability allows a local attacker who has obtained root access on the Android device to bypass the PIN verification step during the PIN change process. By dynamically instrumenting the application—modifying its runtime behavior—the attacker can circumvent the check that normally requires the current PIN to authorize a PIN change. This flaw stems from inadequate enforcement of access control (CWE-284) within the authentication logic, permitting unauthorized modification of the authentication PIN without knowledge of the original PIN. The vulnerability does not require user interaction but does require elevated privileges (root access) on the device, which limits the attack surface to already compromised devices. The CVSS v3.1 base score is 6.0, reflecting medium severity with high impact on confidentiality and integrity but no impact on availability. No known exploits are reported in the wild, and no patches have been linked yet. This vulnerability could allow attackers to take over user accounts by changing authentication credentials, potentially leading to unauthorized financial transactions or data exposure within the Payeer platform.
Potential Impact
For European organizations, especially those in the financial sector or those relying on Payeer for payment processing or wallet services, this vulnerability poses a significant risk to user account security. If an attacker gains root access to a device, they can bypass PIN protections and change authentication credentials, leading to unauthorized access to funds or sensitive financial data. This undermines user trust and could result in financial losses, regulatory penalties under GDPR for data breaches, and reputational damage. The impact is heightened in environments where devices are more likely to be rooted or compromised, such as among tech-savvy users or in organizations with lax device security policies. Since the vulnerability requires local root access, the threat is more relevant in scenarios involving insider threats, lost or stolen devices, or malware that escalates privileges. European organizations with mobile workforces or BYOD policies should be particularly cautious.
Mitigation Recommendations
1. Restrict and monitor root access on Android devices used within the organization to prevent attackers from gaining the necessary privileges to exploit this vulnerability. 2. Implement mobile device management (MDM) solutions that detect and block rooted or jailbroken devices from accessing corporate resources or sensitive applications like Payeer. 3. Employ runtime application self-protection (RASP) or integrity verification mechanisms within the Payeer app to detect and prevent dynamic instrumentation or tampering attempts. 4. Educate users about the risks of rooting devices and encourage use of official, unmodified app versions only. 5. Monitor for unusual PIN change activities or authentication anomalies within Payeer accounts to detect potential exploitation. 6. Coordinate with Payeer to obtain and apply security patches promptly once available. 7. Enforce multi-factor authentication (MFA) where possible to add an additional security layer beyond PIN protection. 8. Regularly audit and update device security policies to minimize the risk of privilege escalation on mobile devices.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- mitre
- Date Reserved
- 2025-08-17T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 68dac2946c49d694f9bd907c
Added to database: 9/29/2025, 5:32:04 PM
Last enriched: 10/6/2025, 6:08:36 PM
Last updated: 11/14/2025, 6:26:34 AM
Views: 40
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-10686: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Creta Testimonial Showcase
UnknownCVE-2025-64444: Improper neutralization of special elements used in an OS command ('OS Command Injection') in Sony Network Communications Inc. NCP-HG100/Cellular model
HighCVE-2025-13161: CWE-23 Relative Path Traversal in IQ Service International IQ-Support
HighCVE-2025-13160: CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere in IQ Service International IQ-Support
MediumCVE-2025-9479: Out of bounds read in Google Chrome
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.