CVE-2005-3146: Low severity StoreBackup StoreBackup vulnerability
Published Oct 5, 2005
·Updated
StoreBackup before 1.19 allows local users to perform unauthorized operations on arbitrary files via a symlink attack on temporary files.
Affected Software
30 affected components
StoreBackup StoreBackup=1.10
StoreBackup StoreBackup=1.12.1
StoreBackup StoreBackup=1.8.1
StoreBackup StoreBackup=1.4
StoreBackup StoreBackup=1.12.2
StoreBackup StoreBackup=1.18.4
StoreBackup StoreBackup=1.17
StoreBackup StoreBackup=1.16
StoreBackup StoreBackup=1.15
StoreBackup StoreBackup=1.6
StoreBackup StoreBackup=1.2
StoreBackup StoreBackup=1.1
StoreBackup StoreBackup=1.8
StoreBackup StoreBackup=1.10.1
StoreBackup StoreBackup=1.3
StoreBackup StoreBackup=1.18.1
StoreBackup StoreBackup=1.9
StoreBackup StoreBackup=1.9.1
StoreBackup StoreBackup=1.14
StoreBackup StoreBackup=1.18.3
StoreBackup StoreBackup=1.16.2
StoreBackup StoreBackup=1.7
StoreBackup StoreBackup=1.11
StoreBackup StoreBackup=1.16.1
StoreBackup StoreBackup=1.12
StoreBackup StoreBackup=1.13
StoreBackup StoreBackup=1.18
StoreBackup StoreBackup=1.18.2
StoreBackup StoreBackup=1.5
SUSE SuSE Linux
Remediation
Patch Available
Event History
Oct 5, 2005
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2005-3146?
CVE-2005-3146 is classified as a moderate severity vulnerability.
2
How do I fix CVE-2005-3146?
To fix CVE-2005-3146, upgrade to StoreBackup version 1.19 or later to mitigate the symlink attack risk.
3
Who is affected by CVE-2005-3146?
CVE-2005-3146 affects local users of StoreBackup versions prior to 1.19.
4
What type of attack is described in CVE-2005-3146?
CVE-2005-3146 describes a symlink attack that allows unauthorized operations on arbitrary files.
5
Is there a known workaround for CVE-2005-3146?
There are no official workarounds for CVE-2005-3146; upgrading to a patched version is recommended.