CVE-2005-3148: Medium severity StoreBackup StoreBackup vulnerability
Published Oct 5, 2005
·Updated
StoreBackup before 1.19 does not properly set the uid and guid for symbolic links (1) that are backed up by storeBackup.pl, or (2) recovered by storeBackupRecover.pl, which could cause files to be restored with incorrect ownership.
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
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-3148?
CVE-2005-3148 is rated as a medium severity vulnerability.
2
How do I fix CVE-2005-3148?
To fix CVE-2005-3148, upgrade to StoreBackup version 1.19 or later.
3
What versions of StoreBackup are affected by CVE-2005-3148?
CVE-2005-3148 affects all StoreBackup versions prior to 1.19.
4
What issues does CVE-2005-3148 cause?
CVE-2005-3148 can lead to restored files having incorrect ownership due to improper uid and guid settings.
5
Is CVE-2005-3148 fixed in newer releases of StoreBackup?
Yes, CVE-2005-3148 is fixed in StoreBackup version 1.19 and subsequent releases.