# CVE-2013-6079: Memory corruption in n/a

> Local attackers can cause a crash or execute code via buffer overflow in license fields of Easy LAN Folder Share.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g4pm-5hhr-6m2p

## What is CVE-2013-6079?

CVE-2013-6079 is a high-severity memory corruption vulnerability in n/a, published on 11 Oct 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-6079?

It affects 1 product.


Products: Mostgear Easy Lan Folder Share.

## How do I fix CVE-2013-6079?

No fix has been published for CVE-2013-6079 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-6079 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6079 exists.

Public exploit code:

- Easy LAN Folder Share 3.2.0.100 - Buffer Overflow (exploitdb)
- Easy LAN Folder Share 3.2.0.100 - Local Buffer Overflow (SEH) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6079 and fix it if it is affected.

What it is: CVE-2013-6079 is a high-severity memory corruption vulnerability in n/a, published on 11 Oct 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6079 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-6079/ (Markdown: https://insights.sbomify.com/CVE-2013-6079/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-6079
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-6079
- OSV: https://osv.dev/vulnerability/CVE-2013-6079

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-6079/
Summaries are generated and may contain mistakes; the official description above is the record.