CVE-2010-3488 json
Directory traversal vulnerability in QuickShare 1.0 allows remote attackers to read arbitrary files via a ... (triple dot) in the URL.
published 16y ago modified 4mo ago also EUVD-2010-3486
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Directory traversal vulnerability in QuickShare 1.0 allows remote attackers to read arbitrary files via a ... (triple dot) in the URL.
Is CVE-2010-3488 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.76% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- johnleitch.net http://www.johnleitch.net/Vulnerabilities/QuickShare.1.0.Directory.Traversal/38 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/43258 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1009-exploits/quickshare10-traversal.txt referenced PoC, tagged "exploit" by a source, unverified
- osvdb.org http://osvdb.org/68089 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
johnleitch.net
/Vulnerabilities/QuickShare.1.0.Directory.Traversal/38
exploit
-
securityfocus.com
/bid/43258
vdb-entry, exploit
-
packetstormsecurity.org
/1009-exploits/quickshare10-traversal.txt
exploit
-
osvdb.org
/68089
vdb-entry, exploit
-
secunia.com
/advisories/41474
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/61857
vdb-entry
Sources
- CVE List CVE-2010-3488
- NVD CVE-2010-3488
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.