Menu

Star on GitHub · 3.2k

CVE-2005-2655

10.0 · HIGH

lockmail in maildrop before 1.5.3 does not drop privileges before executing commands, which allows local users to gain privileges via command line arguments.

Published Aug 30, 2005maildropEPSS 1.48%

Overview

CVE-2005-2655 is a high-severity vulnerability affecting maildrop maildrop. It was published on August 30, 2005 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

lockmail in maildrop before 1.5.3 does not drop privileges before executing commands, which allows local users to gain privileges via command line arguments.

Remediation

Check the references section for vendor advisories and patches from maildrop. Update maildrop to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2005-2655?

CVE-2005-2655 is a high-severity vulnerability affecting maildrop maildrop. It was published on August 30, 2005 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2005-2655?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2005-2655?

Check the references section for vendor advisories and patches from maildrop. Update maildrop to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2005-2655?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-2655 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2005

View all