CVE-2025-21472

5.5 MEDIUM

📋 TL;DR

This vulnerability allows unauthorized access to sensitive information when logs are captured, as eSE debug messages containing potentially sensitive data are logged. It affects systems using Qualcomm chipsets with eSE functionality. The risk primarily impacts devices where debug logging is enabled.

💻 Affected Systems

Products:
  • Qualcomm chipsets with eSE (embedded Secure Element) functionality
Versions: Specific versions not detailed in reference; consult Qualcomm August 2025 bulletin
Operating Systems: Android and other OS using Qualcomm chipsets
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability manifests when debug logging is enabled for eSE components.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could extract cryptographic keys, authentication tokens, or other sensitive data from debug logs, potentially leading to complete system compromise.

🟠

Likely Case

Limited information disclosure of non-critical debug data, possibly revealing system state or configuration details.

🟢

If Mitigated

Minimal impact if debug logging is disabled or logs are properly secured with restricted access.

🌐 Internet-Facing: LOW - This vulnerability requires local access or ability to capture logs, not directly exploitable over internet.
🏢 Internal Only: MEDIUM - Internal attackers with access to logs could extract sensitive information from debug messages.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires ability to access or capture system logs where debug messages are stored.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to Qualcomm August 2025 security bulletin for specific patched versions

Vendor Advisory: https://docs.qualcomm.com/product/publicresources/securitybulletin/august-2025-bulletin.html

Restart Required: No

Instructions:

1. Check Qualcomm August 2025 security bulletin for affected chipsets. 2. Apply firmware/software updates from device manufacturer. 3. Verify debug logging settings are properly configured post-update.

🔧 Temporary Workarounds

Disable eSE debug logging

Android

Prevents sensitive information from being written to logs by disabling debug logging for eSE components.

adb shell setprop persist.vendor.qsee.logs.enable 0
adb shell reboot

🧯 If You Can't Patch

  • Disable all unnecessary debug logging system-wide
  • Implement strict access controls on log files and directories

🔍 How to Verify

Check if Vulnerable:

Check if eSE debug logging is enabled: adb shell getprop persist.vendor.qsee.logs.enable

Check Version:

adb shell getprop ro.build.version.security_patch

Verify Fix Applied:

Verify debug logging is disabled and check system logs for eSE debug messages

📡 Detection & Monitoring

Log Indicators:

  • eSE debug messages in system logs
  • Unexpected access to log files containing debug information

Network Indicators:

  • Unusual log file transfers or exfiltration

SIEM Query:

source="system_logs" AND "eSE" AND "debug"

🔗 References

📤 Share & Export