CVE-1999-1353 in MsgCore
Summary
by MITRE
Nosque MsgCore 2.14 stores passwords in cleartext: (1) the administrator password in the AdmPasswd registry key, and (2) user passwords in the Userbase.dbf data file, which could allow local users to gain privileges.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 04/19/2026
This vulnerability resides in Nosque MsgCore 2.14 software where sensitive authentication credentials are stored in an insecure manner that fundamentally compromises system security. The flaw manifests in two distinct locations within the application's configuration and data storage mechanisms, creating multiple attack vectors for local adversaries seeking unauthorized access. The primary issue involves the administrator password being stored in cleartext within the Windows registry under the AdmPasswd key, while user passwords are similarly stored in the Userbase.dbf database file without any form of cryptographic protection or obfuscation.
The technical implementation of this vulnerability stems from poor security practices in credential storage design, where the application fails to implement proper password hashing or encryption mechanisms for sensitive data. This represents a classic violation of security best practices and aligns with CWE-312, which addresses the exposure of sensitive information through cleartext storage. The vulnerability affects local users who have access to the system, as they can directly read these cleartext credentials without requiring any sophisticated attack techniques. The registry key approach provides immediate access to administrative privileges, while the database file allows attackers to enumerate user credentials and potentially escalate their privileges within the system.
The operational impact of this vulnerability extends beyond simple credential theft, as it enables local privilege escalation attacks that can compromise the entire system. An attacker with local access can leverage these cleartext credentials to assume administrative roles, potentially leading to full system compromise and persistence. This vulnerability directly relates to ATT&CK technique T1078 which covers valid accounts and privilege escalation through legitimate credentials. The exposure of user passwords in the database file also creates opportunities for credential reuse attacks across different systems and applications, amplifying the potential damage. Additionally, the presence of these cleartext credentials in multiple locations increases the attack surface and makes the system more susceptible to various exploitation techniques.
Mitigation strategies should focus on immediate remediation through patching or upgrading to versions that properly encrypt or hash password storage. Organizations should implement registry key permissions controls to limit access to the AdmPasswd registry entry and ensure that the Userbase.dbf file is protected with appropriate file system permissions. The system should be configured to enforce password hashing with strong cryptographic algorithms and proper salting mechanisms. Regular security audits should verify that no cleartext credentials exist in system files or configuration stores, and monitoring should be implemented to detect unauthorized access attempts to sensitive registry keys or database files. Additionally, implementing principle of least privilege access controls and regular credential rotation policies will help reduce the impact of such vulnerabilities.