CVE-2010-1511: Path Traversal

Published 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.

Affected Software

112 affected components
KDE KGet=2.4.2
KDE KDE SC=2.2.0
KDE KDE SC=3.5.10
KDE KDE SC=4.0.0
KDE KDE SC=4.0.0-alpha1
KDE KDE SC=4.0.0-alpha2
KDE KDE SC=4.0.0-beta1
KDE KDE SC=4.0.0-beta2
KDE KDE SC=4.0.0-beta3
KDE KDE SC=4.0.0-beta4
KDE KDE SC=4.0.0-rc1
KDE KDE SC=4.0.0-rc2
KDE KDE SC=4.0.1
KDE KDE SC=4.0.2
KDE KDE SC=4.0.3
KDE KDE SC=4.0.4
KDE KDE SC=4.0.5
KDE KDE SC=4.1.0
KDE KDE SC=4.1.0-alpha1
KDE KDE SC=4.1.0-beta1
KDE KDE SC=4.1.0-beta2
KDE KDE SC=4.1.0-rc
KDE KDE SC=4.1.1
KDE KDE SC=4.1.2
KDE KDE SC=4.1.3
KDE KDE SC=4.1.4
KDE KDE SC=4.1.80
KDE KDE SC=4.1.85
KDE KDE SC=4.1.96
KDE KDE SC=4.2-beta2
KDE KDE SC=4.2-rc
KDE KDE SC=4.2.0
KDE KDE SC=4.2.1
KDE KDE SC=4.2.2
KDE KDE SC=4.2.3
KDE KDE SC=4.2.4
KDE KDE SC=4.3.0
KDE KDE SC=4.3.0-beta1
KDE KDE SC=4.3.0-beta3
KDE KDE SC=4.3.0-rc1
KDE KDE SC=4.3.0-rc2
KDE KDE SC=4.3.0-rc3
KDE KDE SC=4.3.1
KDE KDE SC=4.3.2
KDE KDE SC=4.3.3
KDE KDE SC=4.3.4
KDE KDE SC=4.3.5
KDE KDE SC=4.4.0
KDE KDE SC=4.4.0-beta1
KDE KDE SC=4.4.0-beta2
KDE KDE SC=4.4.0-rc1
KDE KDE SC=4.4.0-rc2
KDE KDE SC=4.4.0-rc3
KDE KDE SC=4.4.1
KDE KDE SC=4.4.2
KDE KDE SC=4.4.3
All of the following
KDE KGet=2.4.2
Any of the following
KDE KDE SC=2.2.0
KDE KDE SC=3.5.10
KDE KDE SC=4.0.0
KDE KDE SC=4.0.0-alpha1
KDE KDE SC=4.0.0-alpha2
KDE KDE SC=4.0.0-beta1
KDE KDE SC=4.0.0-beta2
KDE KDE SC=4.0.0-beta3
KDE KDE SC=4.0.0-beta4
KDE KDE SC=4.0.0-rc1
KDE KDE SC=4.0.0-rc2
KDE KDE SC=4.0.1
KDE KDE SC=4.0.2
KDE KDE SC=4.0.3
KDE KDE SC=4.0.4
KDE KDE SC=4.0.5
KDE KDE SC=4.1.0
KDE KDE SC=4.1.0-alpha1
KDE KDE SC=4.1.0-beta1
KDE KDE SC=4.1.0-beta2
KDE KDE SC=4.1.0-rc
KDE KDE SC=4.1.1
KDE KDE SC=4.1.2
KDE KDE SC=4.1.3
KDE KDE SC=4.1.4
KDE KDE SC=4.1.80
KDE KDE SC=4.1.85
KDE KDE SC=4.1.96
KDE KDE SC=4.2-beta2
KDE KDE SC=4.2-rc
KDE KDE SC=4.2.0
KDE KDE SC=4.2.1
KDE KDE SC=4.2.2
KDE KDE SC=4.2.3
KDE KDE SC=4.2.4
KDE KDE SC=4.3.0
KDE KDE SC=4.3.0-beta1
KDE KDE SC=4.3.0-beta3
KDE KDE SC=4.3.0-rc1
KDE KDE SC=4.3.0-rc2
KDE KDE SC=4.3.0-rc3
KDE KDE SC=4.3.1
KDE KDE SC=4.3.2
KDE KDE SC=4.3.3
KDE KDE SC=4.3.4
KDE KDE SC=4.3.5
KDE KDE SC=4.4.0
KDE KDE SC=4.4.0-beta1
KDE KDE SC=4.4.0-beta2
KDE KDE SC=4.4.0-rc1
KDE KDE SC=4.4.0-rc2
KDE KDE SC=4.4.0-rc3
KDE KDE SC=4.4.1
KDE KDE SC=4.4.2
KDE KDE SC=4.4.3

Event History

May 13, 2010
CVE Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionSeverityWeakness
May 17, 2010
CVE Published
via MITRE·08:42 PM
Data Sourced
via MITRE·08:42 PM
Description
Data Sourced
09:00 PM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·09:00 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2010-1511?

CVE-2010-1511 is considered a medium severity vulnerability.

2

How do I fix CVE-2010-1511?

To fix CVE-2010-1511, upgrade to a fixed version of KGet, which addresses the file overwrite issue.

3

What versions of KGet are affected by CVE-2010-1511?

Versions from KGet 2.4.2 to KDE SC 4.4.3 are affected by CVE-2010-1511.

4

What impact does CVE-2010-1511 have on users?

CVE-2010-1511 allows remote attackers to overwrite arbitrary files on a user's system.

5

Do I need to take immediate action for CVE-2010-1511?

Yes, immediate action is recommended to prevent potential data loss from CVE-2010-1511.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203