CVE-1999-1366: Pegasus e-mail client 3.0 and earlier uses weak encryption to store POP3 passwords in the pmail.ini
Pegasus e-mail client 3.0 and earlier uses weak encryption to store POP3 passwords in the pmail.ini file, which allows local users to easily decrypt the passwords and read e-mail.
AI Analysis
Technical Summary
CVE-1999-1366 identifies a vulnerability in Pegasus Mail client version 3.0 and earlier, where the application uses weak encryption to store POP3 passwords within the pmail.ini configuration file. This weak encryption scheme allows local users with access to the file system to easily decrypt and retrieve stored passwords. Since the passwords are stored locally and protected only by a weak cryptographic method, an attacker or unauthorized user who gains local access to the system can compromise the confidentiality of the user's email credentials. This vulnerability does not require network access or remote exploitation; it is purely a local privilege issue. The weakness impacts the confidentiality and integrity of email accounts by exposing credentials that could be used to access email messages or impersonate the user. The vulnerability has a CVSS score of 3.6 (low severity), reflecting that it requires local access, has low attack complexity, no authentication is needed beyond local access, and impacts confidentiality and integrity but not availability. No patches or fixes are available for this issue, and there are no known exploits in the wild. Given the age of the vulnerability (published in 1999) and the product version affected, this issue is primarily relevant to legacy systems still running Pegasus Mail 3.0 or earlier.
Potential Impact
For European organizations, the impact of this vulnerability is generally low due to the age of the software and the requirement for local access to exploit it. However, organizations that maintain legacy systems or have users still running Pegasus Mail 3.0 or earlier could be at risk of credential compromise if an attacker gains local access to those systems. Compromised POP3 credentials could lead to unauthorized access to email accounts, potentially exposing sensitive communications and internal information. This could affect confidentiality and integrity of email data, which is critical for business operations and compliance with data protection regulations such as GDPR. The vulnerability does not allow remote exploitation, so the risk is limited to insider threats or attackers who have already breached perimeter defenses. Nonetheless, any exposure of email credentials can facilitate further lateral movement or phishing attacks within an organization.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should first identify any systems still running Pegasus Mail version 3.0 or earlier and plan to upgrade to a more recent, supported email client that uses strong encryption for credential storage. If upgrading is not immediately possible, restrict local access to affected systems by enforcing strict access controls and monitoring for unauthorized access attempts. Encrypt the entire user profile or home directory to protect configuration files from unauthorized reading. Educate users about the risks of storing passwords in weakly encrypted files and encourage the use of secure password management solutions. Additionally, implement endpoint detection and response (EDR) tools to detect suspicious local activity that could indicate attempts to access or extract credentials. Regularly audit systems for legacy software and remove or replace outdated applications to reduce attack surface.
Affected Countries
United Kingdom, Germany, France, Italy, Spain, Netherlands, Belgium
CVE-1999-1366: Pegasus e-mail client 3.0 and earlier uses weak encryption to store POP3 passwords in the pmail.ini
Description
Pegasus e-mail client 3.0 and earlier uses weak encryption to store POP3 passwords in the pmail.ini file, which allows local users to easily decrypt the passwords and read e-mail.
AI-Powered Analysis
Technical Analysis
CVE-1999-1366 identifies a vulnerability in Pegasus Mail client version 3.0 and earlier, where the application uses weak encryption to store POP3 passwords within the pmail.ini configuration file. This weak encryption scheme allows local users with access to the file system to easily decrypt and retrieve stored passwords. Since the passwords are stored locally and protected only by a weak cryptographic method, an attacker or unauthorized user who gains local access to the system can compromise the confidentiality of the user's email credentials. This vulnerability does not require network access or remote exploitation; it is purely a local privilege issue. The weakness impacts the confidentiality and integrity of email accounts by exposing credentials that could be used to access email messages or impersonate the user. The vulnerability has a CVSS score of 3.6 (low severity), reflecting that it requires local access, has low attack complexity, no authentication is needed beyond local access, and impacts confidentiality and integrity but not availability. No patches or fixes are available for this issue, and there are no known exploits in the wild. Given the age of the vulnerability (published in 1999) and the product version affected, this issue is primarily relevant to legacy systems still running Pegasus Mail 3.0 or earlier.
Potential Impact
For European organizations, the impact of this vulnerability is generally low due to the age of the software and the requirement for local access to exploit it. However, organizations that maintain legacy systems or have users still running Pegasus Mail 3.0 or earlier could be at risk of credential compromise if an attacker gains local access to those systems. Compromised POP3 credentials could lead to unauthorized access to email accounts, potentially exposing sensitive communications and internal information. This could affect confidentiality and integrity of email data, which is critical for business operations and compliance with data protection regulations such as GDPR. The vulnerability does not allow remote exploitation, so the risk is limited to insider threats or attackers who have already breached perimeter defenses. Nonetheless, any exposure of email credentials can facilitate further lateral movement or phishing attacks within an organization.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should first identify any systems still running Pegasus Mail version 3.0 or earlier and plan to upgrade to a more recent, supported email client that uses strong encryption for credential storage. If upgrading is not immediately possible, restrict local access to affected systems by enforcing strict access controls and monitoring for unauthorized access attempts. Encrypt the entire user profile or home directory to protect configuration files from unauthorized reading. Educate users about the risks of storing passwords in weakly encrypted files and encourage the use of secure password management solutions. Additionally, implement endpoint detection and response (EDR) tools to detect suspicious local activity that could indicate attempts to access or extract credentials. Regularly audit systems for legacy software and remove or replace outdated applications to reduce attack surface.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Threat ID: 682ca32cb6fd31d6ed7df000
Added to database: 5/20/2025, 3:43:40 PM
Last enriched: 7/1/2025, 5:55:01 PM
Last updated: 7/25/2025, 11:05:28 PM
Views: 12
Related Threats
CVE-2025-8774: Observable Timing Discrepancy in riscv-boom SonicBOOM
LowVulnerability Management Program - How to implement SLA and its processes
LowCVE-2025-8751: Cross Site Scripting in Protected Total WebShield Extension
LowCVE-2025-54940: Code injection in WPEngine, Inc. Advanced Custom Fields
LowCVE-2025-8708: Deserialization in Antabot White-Jotter
LowActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.