cve.bz

CVE-2011-1586 kde kde sc: Path traversal

no score yetEPSS 3.1%Fix available

kde kde sc: no CVSS score yet. EPSS 3.1% estimated probability of exploitation activity in the next 30 days.

On this page
Directory traversal vulnerability in the KGetMetalink::File::isValidNameAttr function in ui/metalinkcreator/metalinker.cpp in KGet in KDE SC 4.6.2 and earlier allows remote attackers to create arbitrary files via a .. (dot dot) in the name attribute of a file element in a metalink file. NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-1000.
EPSS
3.1% (unchanged from 3.1% a week ago; 3.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 88th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2011-1586 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2011-1586?via=ask-ai-copy and https://cve.bz/cve/CVE-2011-1586?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2011-1586 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
kde:kde_scthrough 4.6.2
kde:kde_sc2.2.0
kde:kde_sc3.5.10
kde:kde_sc4.0.0
kde:kde_sc4.0.0:alpha1
kde:kde_sc4.0.0:alpha2
kde:kde_sc4.0.0:beta1
kde:kde_sc4.0.0:beta2
kde:kde_sc4.0.0:beta3
kde:kde_sc4.0.0:beta4
kde:kde_sc4.0.0:rc1
kde:kde_sc4.0.0:rc2
kde:kde_sc4.0.1
kde:kde_sc4.0.2
kde:kde_sc4.0.3
kde:kde_sc4.0.4
kde:kde_sc4.0.5
kde:kde_sc4.1.0
kde:kde_sc4.1.0:alpha1
kde:kde_sc4.1.0:beta1
kde:kde_sc4.1.0:beta2
kde:kde_sc4.1.0:rc
kde:kde_sc4.1.1
kde:kde_sc4.1.2
kde:kde_sc4.1.3
kde:kde_sc4.1.4
kde:kde_sc4.1.80
kde:kde_sc4.1.85
kde:kde_sc4.1.96
kde:kde_sc4.2:beta2
kde:kde_sc4.2:rc
kde:kde_sc4.2.0
kde:kde_sc4.2.1
kde:kde_sc4.2.2
kde:kde_sc4.2.3
kde:kde_sc4.2.4
kde:kde_sc4.3.0
kde:kde_sc4.3.0:beta1
kde:kde_sc4.3.0:beta3
kde:kde_sc4.3.0:rc1
kde:kde_sc4.3.0:rc2
kde:kde_sc4.3.0:rc3
kde:kde_sc4.3.1
kde:kde_sc4.3.2
kde:kde_sc4.3.3
kde:kde_sc4.3.4
kde:kde_sc4.3.5
kde:kde_sc4.4.0
kde:kde_sc4.4.0:beta1
kde:kde_sc4.4.0:beta2
kde:kde_sc4.4.0:rc1
kde:kde_sc4.4.0:rc2
kde:kde_sc4.4.0:rc3
kde:kde_sc4.4.1
kde:kde_sc4.4.2
kde:kde_sc4.4.3
kde:kde_sc4.4.4
kde:kde_sc4.4.5
kde:kde_sc4.5.0
kde:kde_sc4.5.1
kde:kde_sc4.5.2
kde:kde_sc4.5.3
kde:kde_sc4.5.4
kde:kde_sc4.5.5
kde:kde_sc4.6:beta1
kde:kde_sc4.6:beta2
kde:kde_sc4.6:rc1
kde:kde_sc4.6:rc2
kde:kde_sc4.6.0
kde:kde_sc4.6.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatenterprise_linux:6::client, enterprise_linux:6::server, enterprise_linux:6::workstationkdenetwork, kdenetwork-libs, kdenetwork-devel and 1 more7:4.3.4-11.el6_0.1RHSA-2011:0465

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Important.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6kdenetwork-7:4.3.4-11.el6_0.1Fixed 2011-04-21RHSA-2011:0465

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2011-1586.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON