First published: Thu May 13 2010(Updated: )
KGet 2.4.2 in KDE SC 4.0.0 through 4.4.3 does not properly request download confirmation from the user, which makes it easier for remote attackers to overwrite arbitrary files via a crafted metalink file.
Credit: PSIRT-CNA@flexerasoftware.com
Affected Software | Affected Version | How to fix |
---|---|---|
Krzysztof Kozlowski Konwert | =2.4.2 | |
KDE SC | =2.2.0 | |
KDE SC | =3.5.10 | |
KDE SC | =4.0.0 | |
KDE SC | =4.0.0-alpha1 | |
KDE SC | =4.0.0-alpha2 | |
KDE SC | =4.0.0-beta1 | |
KDE SC | =4.0.0-beta2 | |
KDE SC | =4.0.0-beta3 | |
KDE SC | =4.0.0-beta4 | |
KDE SC | =4.0.0-rc1 | |
KDE SC | =4.0.0-rc2 | |
KDE SC | =4.0.1 | |
KDE SC | =4.0.2 | |
KDE SC | =4.0.3 | |
KDE SC | =4.0.4 | |
KDE SC | =4.0.5 | |
KDE SC | =4.1.0 | |
KDE SC | =4.1.0-alpha1 | |
KDE SC | =4.1.0-beta1 | |
KDE SC | =4.1.0-beta2 | |
KDE SC | =4.1.0-rc | |
KDE SC | =4.1.1 | |
KDE SC | =4.1.2 | |
KDE SC | =4.1.3 | |
KDE SC | =4.1.4 | |
KDE SC | =4.1.80 | |
KDE SC | =4.1.85 | |
KDE SC | =4.1.96 | |
KDE SC | =4.2-beta2 | |
KDE SC | =4.2-rc | |
KDE SC | =4.2.0 | |
KDE SC | =4.2.1 | |
KDE SC | =4.2.2 | |
KDE SC | =4.2.3 | |
KDE SC | =4.2.4 | |
KDE SC | =4.3.0 | |
KDE SC | =4.3.0-beta1 | |
KDE SC | =4.3.0-beta3 | |
KDE SC | =4.3.0-rc1 | |
KDE SC | =4.3.0-rc2 | |
KDE SC | =4.3.0-rc3 | |
KDE SC | =4.3.1 | |
KDE SC | =4.3.2 | |
KDE SC | =4.3.3 | |
KDE SC | =4.3.4 | |
KDE SC | =4.3.5 | |
KDE SC | =4.4.0 | |
KDE SC | =4.4.0-beta1 | |
KDE SC | =4.4.0-beta2 | |
KDE SC | =4.4.0-rc1 | |
KDE SC | =4.4.0-rc2 | |
KDE SC | =4.4.0-rc3 | |
KDE SC | =4.4.1 | |
KDE SC | =4.4.2 | |
KDE SC | =4.4.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-1511 is considered a medium severity vulnerability.
To fix CVE-2010-1511, upgrade to a fixed version of KGet, which addresses the file overwrite issue.
Versions from KGet 2.4.2 to KDE SC 4.4.3 are affected by CVE-2010-1511.
CVE-2010-1511 allows remote attackers to overwrite arbitrary files on a user's system.
Yes, immediate action is recommended to prevent potential data loss from CVE-2010-1511.