Menu

Star on GitHub · 3.2k

CVE-2005-2211

4.6 · MEDIUM

Backup Manager 0.5.8a creates temporary files insecurely, which allows local users to conduct unauthorized file operations when a user is burning a CDR.

Published Jul 11, 2005sukriaEPSS 0.32%

Overview

CVE-2005-2211 is a medium-severity vulnerability affecting sukria backup_manager. It was published on July 11, 2005 and has a CVSS 2.0 base score of 4.6 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 4.6, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

Backup Manager 0.5.8a creates temporary files insecurely, which allows local users to conduct unauthorized file operations when a user is burning a CDR.

Remediation

Check the references section for vendor advisories and patches from sukria. Update backup_manager 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-2211?

CVE-2005-2211 is a medium-severity vulnerability affecting sukria backup_manager. It was published on July 11, 2005 and has a CVSS 2.0 base score of 4.6 (MEDIUM).

How severe is CVE-2005-2211?

This vulnerability has a CVSS 2.0 base score of 4.6, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

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

Check the references section for vendor advisories and patches from sukria. Update backup_manager 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-2211?

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