CVE-2013-6079 json
Buffer overflow in MostGear Soft Easy LAN Folder Share 3.2.0.100 allows local users to cause a denial of service (application crash) and po…
published 13y ago modified 4mo ago also EUVD-2013-5908
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 2
- Exploit-DB
Summary
Buffer overflow in MostGear Soft Easy LAN Folder Share 3.2.0.100 allows local users to cause a denial of service (application crash) and possibly execute arbitrary code via a long string in the (1) registration code field in the activate license window or the (2) HKLM\SOFTWARE\MostGear\EasyLanFolderShare_V1\License registry key. NOTE: it is not clear from the original report whether this issue crosses privilege boundaries. If not, then it should not be included in CVE.
Is CVE-2013-6079 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 FencerTimeline
- First public exploit (EDB-26214)
- Published
Exploit prediction
1.27% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-27316 Easy LAN Folder Share 3.2.0.100 - Local Buffer Overflow (SEH) local, 2013-08-03
- EDB-26214 Easy LAN Folder Share 3.2.0.100 - Buffer Overflow dos, 2013-06-14
- packetstormsecurity.com http://packetstormsecurity.com/files/122677 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/26214
exploit
-
exploit-db.com
/exploits/27316
exploit
-
packetstormsecurity.com
/files/122677
exploit
-
osvdb.org
/show/osvdb/94390
vdb-entry
Sources
- CVE List CVE-2013-6079
- NVD CVE-2013-6079
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.