CVE-2025-54338

7.5 HIGH

📋 TL;DR

An incorrect access control vulnerability in Desktop Alert PingAlert Application Server versions 6.1.0.11 to 6.1.1.2 allows attackers to access and disclose user password hashes. This affects organizations using these vulnerable versions of the notification/alerting software. Attackers can potentially obtain credential hashes that could be cracked offline.

💻 Affected Systems

Products:
  • Desktop Alert PingAlert Application Server
Versions: 6.1.0.11 to 6.1.1.2
Operating Systems: Windows Server (typical deployment)
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects the Application Server component of PingAlert. The vulnerability exists in access control mechanisms that should restrict hash access.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers obtain user password hashes, crack them offline, gain unauthorized access to systems, and potentially move laterally through the network using compromised credentials.

🟠

Likely Case

Attackers access user password hashes, attempt to crack weaker passwords, and gain unauthorized access to the PingAlert system or other systems where users reuse passwords.

🟢

If Mitigated

With proper network segmentation and strong password policies, attackers may obtain hashes but cannot crack them or use them to access critical systems.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability allows hash disclosure through incorrect access controls, suggesting relatively straightforward exploitation once the attack vector is identified.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.1.1.3 or later

Vendor Advisory: https://desktopalert.net/cve-2025-54338/

Restart Required: Yes

Instructions:

1. Download the latest version from Desktop Alert's official website. 2. Backup current configuration and data. 3. Run the installer to upgrade to version 6.1.1.3 or later. 4. Restart the Application Server service. 5. Verify the upgrade completed successfully.

🔧 Temporary Workarounds

Network Segmentation

all

Restrict network access to the PingAlert Application Server to only trusted internal networks

Firewall Rules

windows

Implement firewall rules to block external access to the Application Server ports

netsh advfirewall firewall add rule name="Block PingAlert External" dir=in action=block protocol=TCP localport=8080,8443 remoteip=any

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach the PingAlert Application Server
  • Enforce strong password policies and consider password rotation for all PingAlert users

🔍 How to Verify

Check if Vulnerable:

Check the PingAlert Application Server version in the administration console or via the installed program details in Windows.

Check Version:

Check the application's About dialog or look at the installed program version in Windows Programs and Features

Verify Fix Applied:

Verify the version shows 6.1.1.3 or higher in the administration interface or program details.

📡 Detection & Monitoring

Log Indicators:

  • Unusual access patterns to user data endpoints
  • Multiple failed authentication attempts followed by successful hash retrieval

Network Indicators:

  • Unusual external connections to PingAlert Application Server ports
  • Traffic patterns suggesting enumeration of user data

SIEM Query:

source="pingalert.log" AND (event="user_hash_access" OR event="unauthorized_data_request")

🔗 References

📤 Share & Export