CVE-2020-5239: Unspecified vulnerability in the fetchmail script in Mailu
In Mailu before version 1.7, an authenticated user can exploit a vulnerability in Mailu fetchmail script and gain full access to a Mailu instance. Mailu servers that have open registration or untrusted users are most impacted. The master and 1.7 branches are patched on our git repository. All Docker images published on docker.io/mailu for tags 1.5, 1.6, 1.7 and master are patched. For detailed instructions about patching and securing the server afterwards, see https://github.com/Mailu/Mailu/issues/1354
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
mailuto a version that resolves this vulnerability.Fixed in 1.7 - Upgrade
Upgrade
mailuto a version that resolves this vulnerability.Fixed in 1.6 - Upgrade
Upgrade
mailuto a version that resolves this vulnerability.Fixed in 1.5 - Compensating control
After patching, ensure Mailu does not allow open registration or untrusted users, since Mailu servers with open registration or untrusted users are most impacted by the fetchmail vulnerability in Mailu before 1.7.
Event History
Frequently Asked Questions
What is the severity of CVE-2020-5239?
CVE-2020-5239 is considered a high severity vulnerability due to the potential for an authenticated user to gain full control of a Mailu instance.
How do I fix CVE-2020-5239?
To fix CVE-2020-5239, upgrade to Mailu version 1.7 or later, as the vulnerability has been patched in these releases.
Who is most affected by CVE-2020-5239?
Mailu servers that allow open registration or have untrusted users are the most affected by CVE-2020-5239.
What kind of access can be gained through CVE-2020-5239?
Exploitation of CVE-2020-5239 can allow an authenticated user to gain full access to the Mailu instance, including all user data.
Is there a workaround for CVE-2020-5239?
There are no known effective workarounds for CVE-2020-5239; upgrading to a patched version is the recommended solution.