What is the severity of CVE-2005-1856?

CVE-2005-1856 is considered a moderate severity vulnerability due to its potential for local file overwrite via a symlink attack.

How do I mitigate CVE-2005-1856?

To mitigate CVE-2005-1856, upgrade to backup-manager version 0.5.8 or later where this vulnerability is fixed.

Which versions of backup-manager are affected by CVE-2005-1856?

Backup-manager versions 0.5.6 and 0.5.7 are vulnerable to CVE-2005-1856.

What is the nature of the vulnerability in CVE-2005-1856?

CVE-2005-1856 allows local users to perform a symlink attack due to the use of a fixed filename in a world-writable directory for logging.

Can CVE-2005-1856 be exploited remotely?

No, CVE-2005-1856 is a local vulnerability that requires local access to exploit.

Vulnerability/
CVE-2005-1856

low

2.1

CWE

NVD-CWE-Other

29/8/2005

17/9/2024

CVE-2005-1856

First published: Mon Aug 29 2005(Updated: )

The CD-burning feature in backup-manager 0.5.8 and earlier uses a fixed filename in a world-writable directory for logging, which allows local users to overwrite files via a symlink attack.

Credit: security@debian.org

Affected Software	Affected Version	How to fix
sukria Backup Manager	=0.5.6
sukria Backup Manager	=0.5.7
sukria Backup Manager	=0.5.7
sukria Backup Manager	=0.5.6

Remedy

http://www.debian.org/security/2005/dsa-787

Never miss a vulnerability like this again

Reference Links

http://www.debian.org/security/2005/dsa-787

Frequently Asked Questions

What is the severity of CVE-2005-1856?
CVE-2005-1856 is considered a moderate severity vulnerability due to its potential for local file overwrite via a symlink attack.
How do I mitigate CVE-2005-1856?
To mitigate CVE-2005-1856, upgrade to backup-manager version 0.5.8 or later where this vulnerability is fixed.
Which versions of backup-manager are affected by CVE-2005-1856?
Backup-manager versions 0.5.6 and 0.5.7 are vulnerable to CVE-2005-1856.
What is the nature of the vulnerability in CVE-2005-1856?
CVE-2005-1856 allows local users to perform a symlink attack due to the use of a fixed filename in a world-writable directory for logging.
Can CVE-2005-1856 be exploited remotely?
No, CVE-2005-1856 is a local vulnerability that requires local access to exploit.

agent/softwarecombine
agent/type
agent/severity
agent/weakness
agent/remedy
agent/references
agent/author
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/sukria
canonical/sukria backup manager
version/sukria backup manager/0.5.6
version/sukria backup manager/0.5.7

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2005-1856?
CVE-2005-1856 is considered a moderate severity vulnerability due to its potential for local file overwrite via a symlink attack.
How do I mitigate CVE-2005-1856?
To mitigate CVE-2005-1856, upgrade to backup-manager version 0.5.8 or later where this vulnerability is fixed.
Which versions of backup-manager are affected by CVE-2005-1856?
Backup-manager versions 0.5.6 and 0.5.7 are vulnerable to CVE-2005-1856.
What is the nature of the vulnerability in CVE-2005-1856?
CVE-2005-1856 allows local users to perform a symlink attack due to the use of a fixed filename in a world-writable directory for logging.
Can CVE-2005-1856 be exploited remotely?
No, CVE-2005-1856 is a local vulnerability that requires local access to exploit.