Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13524: CWE-404 Improper Resource Shutdown or Release in AWS Wickr

0
Medium
VulnerabilityCVE-2025-13524cvecve-2025-13524cwe-404
Published: Fri Nov 21 2025 (11/21/2025, 20:03:54 UTC)
Source: CVE Database V5
Vendor/Project: AWS
Product: Wickr

Description

Improper resource release in the call termination process in AWS Wickr before version 6.62.13 on Windows, macOS and Linux may allow a call participant to continue receiving audio input from another user after they close their call window. This issue occurs under certain conditions, which require the affected user to take a particular action within the application To mitigate this issue, users should upgrade AWS Wickr, Wickr Gov and Wickr Enterprise desktop version to version 6.62.13.

AI-Powered Analysis

AILast updated: 11/21/2025, 20:13:51 UTC

Technical Analysis

CVE-2025-13524 is a vulnerability classified under CWE-404 (Improper Resource Shutdown or Release) affecting AWS Wickr desktop clients on Windows, macOS, and Linux platforms before version 6.62.13. The issue arises during the call termination process where the application fails to properly release audio input resources. Specifically, after a user closes their call window, under certain conditions requiring specific user actions within the application, a call participant may continue to receive audio input from another user. This improper resource release leads to unintended audio data leakage, compromising confidentiality. The vulnerability requires the affected user to have local privileges and perform particular interactions in the app, indicating that exploitation is not fully remote and involves user interaction. The CVSS v3.1 score is 5.7 (medium severity), reflecting network attack vector, low attack complexity, requiring privileges and user interaction, with high confidentiality impact but no integrity or availability impact. No known exploits have been reported in the wild, and AWS has addressed the issue by releasing version 6.62.13 of Wickr, Wickr Gov, and Wickr Enterprise desktop clients. The vulnerability is significant in environments where secure communications and privacy are critical, as it may allow unauthorized audio monitoring after call termination.

Potential Impact

For European organizations, this vulnerability poses a confidentiality risk by potentially exposing sensitive audio communications after a call has ostensibly ended. This could lead to unauthorized disclosure of proprietary information, personal data, or strategic discussions, which is particularly concerning under GDPR and other privacy regulations. Organizations in sectors such as government, finance, healthcare, and critical infrastructure that rely on AWS Wickr for secure messaging and calls may face reputational damage and regulatory penalties if audio data leakage occurs. The requirement for user interaction and local privileges somewhat limits the attack surface but does not eliminate risk, especially in insider threat scenarios or compromised endpoints. The lack of integrity and availability impact reduces the risk of system disruption but does not diminish the confidentiality concerns. Prompt patching is essential to maintain compliance and trust in secure communications.

Mitigation Recommendations

European organizations should immediately upgrade all AWS Wickr desktop clients (including Wickr Gov and Wickr Enterprise) to version 6.62.13 or later to remediate this vulnerability. Beyond patching, organizations should enforce strict endpoint security controls to prevent unauthorized local access and monitor user activity for suspicious behavior that might exploit this flaw. User training should emphasize proper call termination procedures and awareness of potential residual audio capture risks. Network segmentation and application whitelisting can reduce exposure. Additionally, organizations should audit and review call logs and access controls to detect any anomalous audio data access. Implementing Data Loss Prevention (DLP) solutions that monitor audio streams may provide an additional layer of defense. Finally, ensure that incident response plans include scenarios involving potential audio data leakage.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
AMZN
Date Reserved
2025-11-21T19:40:09.924Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6920c6d9d9b8477547869881

Added to database: 11/21/2025, 8:08:57 PM

Last enriched: 11/21/2025, 8:13:51 PM

Last updated: 11/22/2025, 1:02:42 AM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats