# CVE-2007-1682: Memory corruption in n/a

> Remote attackers can execute arbitrary code via stack-based buffer overflows in the SoftArtisans XFile ActiveX control, requiring user interaction to trigger.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7j4x-6x3f-7phh

## What is CVE-2007-1682?

CVE-2007-1682 is a critical memory corruption vulnerability in n/a, published on 27 Aug 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple stack-based buffer overflows in the FileManager ActiveX control in SAFmgPws.dll in SoftArtisans XFile before 2.4.0 allow remote attackers to execute arbitrary code via unspecified calls to the (1) BuildPath, (2) GetDriveName, (3) DriveExists, or (4) DeleteFile method.

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

## Which versions are affected by CVE-2007-1682?

It affects 1 product.


Products: Softartisans Xfile.

## How do I fix CVE-2007-1682?

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

## Is CVE-2007-1682 being exploited?

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

Public exploit code:

- SoftArtisans XFile FileManager ActiveX Control Buffer Overflow (metasploit)
- SoftArtisans XFile FileManager - ActiveX Control Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1682 and fix it if it is affected.

What it is: CVE-2007-1682 is a critical memory corruption vulnerability in n/a, published on 27 Aug 2008. An attacker can exploit it over the internet without logging in, 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-2007-1682 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-2007-1682/ (Markdown: https://insights.sbomify.com/CVE-2007-1682/index.md)
```

## Sources

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

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