Menu

Star on GitHub · 3.2k

CVE-2005-1879

5.5 · MEDIUM

LutelWall 0.97 and earlier allows local users to overwrite arbitrary files via a symlink attack on a temporary file created by a system call to wget.

Published Jun 9, 2005lutelCWE-59EPSS 0.39%

Overview

CVE-2005-1879 is a medium-severity vulnerability affecting lutel lutelwall. It was published on June 9, 2005 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

LutelWall 0.97 and earlier allows local users to overwrite arbitrary files via a symlink attack on a temporary file created by a system call to wget.

Remediation

Check the references section for vendor advisories and patches from lutel. Update lutelwall 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
lutellutelwall>= 0, < 0.98Affected

Frequently asked questions

What is CVE-2005-1879?

CVE-2005-1879 is a medium-severity vulnerability affecting lutel lutelwall. It was published on June 9, 2005 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2005-1879?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

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

Check the references section for vendor advisories and patches from lutel. Update lutelwall 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-1879?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-1879 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 MEDIUM CVEs from 2005

View all