CVE-2025-13476: CWE-327 Use of a Broken or Risky Cryptographic Algorithm in Rakuten Viber Rakuten Viber Cloak - Android
Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS ClientHello fingerprint lacking extension diversity, allowing Deep Packet Inspection (DPI) systems to trivially identify and block proxy traffic, undermining censorship circumvention. (CWE-327)
AI Analysis
Technical Summary
CVE-2025-13476 identifies a critical cryptographic vulnerability in Rakuten Viber Cloak mode, specifically in Android version 25.7.2.0g and Windows versions 25.6.0.0 through 25.8.1.0. The vulnerability arises from the use of a static and predictable TLS ClientHello fingerprint that lacks extension diversity. TLS ClientHello messages are part of the handshake process in establishing secure connections, and their fingerprint uniqueness is crucial for evading detection by network monitoring tools. In this case, the static fingerprint allows Deep Packet Inspection (DPI) systems to trivially recognize and block proxy traffic generated by Viber Cloak, which is designed to help users circumvent censorship. This flaw is categorized under CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) and CWE-693 (Protection Mechanism Failure), indicating fundamental weaknesses in cryptographic design and implementation. The vulnerability has a CVSS v3.1 score of 9.8, reflecting its critical severity with network attack vector, low attack complexity, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability. While no active exploits have been reported, the predictable TLS fingerprint significantly undermines the effectiveness of Viber Cloak as a censorship circumvention tool, potentially exposing users to blocking and surveillance. The vulnerability was published on March 5, 2026, and no official patches have been linked yet, emphasizing the urgency for remediation.
Potential Impact
The vulnerability severely impacts users relying on Rakuten Viber Cloak mode for privacy and censorship circumvention. By enabling DPI systems to easily identify and block proxy traffic, it compromises confidentiality by exposing users' attempts to bypass network restrictions, potentially leading to surveillance or punitive actions in restrictive regimes. Integrity and availability are also affected because the blocking of proxy traffic disrupts communication channels, denying users access to censored content or secure messaging. Organizations using Viber Cloak to maintain secure communications may face operational disruptions and data exposure risks. The flaw undermines trust in the product's security guarantees and may force users to seek alternative tools, impacting Rakuten Viber's reputation. Given the critical CVSS score and the nature of the vulnerability, the threat could have widespread consequences in countries with aggressive internet censorship, affecting millions of users and organizations that depend on secure, uncensored communication.
Mitigation Recommendations
1. Immediate mitigation requires users and organizations to monitor Rakuten Viber's official channels for patches addressing this vulnerability and apply updates promptly once available. 2. Until patches are released, users should consider disabling Viber Cloak mode to avoid detection and blocking by DPI systems. 3. Employ alternative circumvention tools that implement randomized or diverse TLS ClientHello fingerprints to evade DPI detection effectively. 4. Network administrators should implement traffic analysis and anomaly detection to identify and alert on suspicious proxy traffic patterns that may be targeted by DPI. 5. Developers should redesign the TLS handshake implementation in Viber Cloak to incorporate extension diversity and fingerprint randomization, following best practices for cryptographic protocol design. 6. Conduct thorough security audits and penetration testing focusing on cryptographic components to prevent similar vulnerabilities. 7. Educate users in high-risk regions about the risks of using vulnerable versions and recommend safer communication alternatives.
Affected Countries
Russia, China, Iran, Turkey, Egypt, United Arab Emirates, Saudi Arabia, Vietnam, Belarus, Ethiopia, Pakistan, North Korea
CVE-2025-13476: CWE-327 Use of a Broken or Risky Cryptographic Algorithm in Rakuten Viber Rakuten Viber Cloak - Android
Description
Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS ClientHello fingerprint lacking extension diversity, allowing Deep Packet Inspection (DPI) systems to trivially identify and block proxy traffic, undermining censorship circumvention. (CWE-327)
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-13476 identifies a critical cryptographic vulnerability in Rakuten Viber Cloak mode, specifically in Android version 25.7.2.0g and Windows versions 25.6.0.0 through 25.8.1.0. The vulnerability arises from the use of a static and predictable TLS ClientHello fingerprint that lacks extension diversity. TLS ClientHello messages are part of the handshake process in establishing secure connections, and their fingerprint uniqueness is crucial for evading detection by network monitoring tools. In this case, the static fingerprint allows Deep Packet Inspection (DPI) systems to trivially recognize and block proxy traffic generated by Viber Cloak, which is designed to help users circumvent censorship. This flaw is categorized under CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) and CWE-693 (Protection Mechanism Failure), indicating fundamental weaknesses in cryptographic design and implementation. The vulnerability has a CVSS v3.1 score of 9.8, reflecting its critical severity with network attack vector, low attack complexity, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability. While no active exploits have been reported, the predictable TLS fingerprint significantly undermines the effectiveness of Viber Cloak as a censorship circumvention tool, potentially exposing users to blocking and surveillance. The vulnerability was published on March 5, 2026, and no official patches have been linked yet, emphasizing the urgency for remediation.
Potential Impact
The vulnerability severely impacts users relying on Rakuten Viber Cloak mode for privacy and censorship circumvention. By enabling DPI systems to easily identify and block proxy traffic, it compromises confidentiality by exposing users' attempts to bypass network restrictions, potentially leading to surveillance or punitive actions in restrictive regimes. Integrity and availability are also affected because the blocking of proxy traffic disrupts communication channels, denying users access to censored content or secure messaging. Organizations using Viber Cloak to maintain secure communications may face operational disruptions and data exposure risks. The flaw undermines trust in the product's security guarantees and may force users to seek alternative tools, impacting Rakuten Viber's reputation. Given the critical CVSS score and the nature of the vulnerability, the threat could have widespread consequences in countries with aggressive internet censorship, affecting millions of users and organizations that depend on secure, uncensored communication.
Mitigation Recommendations
1. Immediate mitigation requires users and organizations to monitor Rakuten Viber's official channels for patches addressing this vulnerability and apply updates promptly once available. 2. Until patches are released, users should consider disabling Viber Cloak mode to avoid detection and blocking by DPI systems. 3. Employ alternative circumvention tools that implement randomized or diverse TLS ClientHello fingerprints to evade DPI detection effectively. 4. Network administrators should implement traffic analysis and anomaly detection to identify and alert on suspicious proxy traffic patterns that may be targeted by DPI. 5. Developers should redesign the TLS handshake implementation in Viber Cloak to incorporate extension diversity and fingerprint randomization, following best practices for cryptographic protocol design. 6. Conduct thorough security audits and penetration testing focusing on cryptographic components to prevent similar vulnerabilities. 7. Educate users in high-risk regions about the risks of using vulnerable versions and recommend safer communication alternatives.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- certcc
- Date Reserved
- 2025-11-20T12:38:19.605Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 69a9c994460e1c85df139316
Added to database: 3/5/2026, 6:21:08 PM
Last enriched: 3/12/2026, 8:36:41 PM
Last updated: 4/19/2026, 4:49:13 PM
Views: 187
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.