CVE-2025-56608

4.2 MEDIUM

📋 TL;DR

This vulnerability allows attackers to potentially bypass authentication in the Corona Virus Tracker App India by exploiting weak MD5 hashing. Attackers could perform replay attacks, credential spoofing, or brute-force attacks to gain unauthorized access. Only users of this specific Android application version are affected.

💻 Affected Systems

Products:
  • Corona Virus Tracker App India
Versions: 1.0
Operating Systems: Android
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable due to hardcoded MD5 usage in authentication.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete authentication bypass allowing unauthorized access to sensitive COVID-19 tracking data and user information.

🟠

Likely Case

Credential theft through hash collision attacks leading to account compromise.

🟢

If Mitigated

Limited impact with proper network controls and monitoring in place.

🌐 Internet-Facing: HIGH - Mobile applications are inherently internet-facing and transmit authentication data over networks.
🏢 Internal Only: LOW - This is a mobile application designed for public use, not internal enterprise systems.

🎯 Exploit Status

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

Exploitation requires intercepting authentication traffic and performing hash collision attacks against MD5.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not specified in references, but vendor should release updated version

Vendor Advisory: https://www.sourcecodester.com/android/14292/android-corona-virus-tracker-app-india-using-b4a.html

Restart Required: No

Instructions:

1. Contact vendor for updated version. 2. Replace MD5 with SHA-256 or stronger algorithm in OkHttpClientWrapper.java. 3. Recompile and distribute updated APK.

🔧 Temporary Workarounds

Network Traffic Encryption

all

Enforce TLS 1.2+ for all app communications to prevent credential interception

🧯 If You Can't Patch

  • Monitor network traffic for unusual authentication patterns
  • Implement rate limiting on authentication endpoints

🔍 How to Verify

Check if Vulnerable:

Decompile APK and search for 'MessageDigest.getInstance("MD5")' in OkHttpClientWrapper.java

Check Version:

Check app version in Android Settings > Apps > Corona Virus Tracker App India

Verify Fix Applied:

Verify updated APK uses SHA-256 or stronger algorithm in authentication code

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed authentication attempts from same source
  • Successful logins with unusual timing patterns

Network Indicators:

  • Repeated authentication requests with same hash values
  • Unencrypted authentication traffic

SIEM Query:

source="app_server" AND (event="authentication_failure" count>10 within 5min OR event="authentication_success" from new_device)

🔗 References

📤 Share & Export