# CVE-2007-3785: Path traversal in n/a

> Remote attackers can overwrite arbitrary files via path traversal in the SaveToFile method of an ActiveX control, requiring user interaction.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:N/I:P/A:P`)
- **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:** 15 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wp8h-hh6c-99qc

## What is CVE-2007-3785?

CVE-2007-3785 is a medium-severity path traversal vulnerability in n/a, published on 15 Jul 2007. 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

Absolute path traversal vulnerability in a certain ActiveX control in PGPBBox.dll in EldoS SecureBlackbox (sbb) 5.1.0.112 allows remote attackers to create or overwrite arbitrary files via a full pathname in the argument to the SaveToFile method.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

It affects 1 product.


Products: Eldos Corporation Secureblackbox.

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

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

## Is CVE-2007-3785 being exploited?

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

Public exploit code:

- SecureBlackbox 'PGPBBox.dll 5.1.0.112' - Arbitrary Data Write (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3785 is a medium-severity path traversal vulnerability in n/a, published on 15 Jul 2007. 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-3785 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-3785/ (Markdown: https://insights.sbomify.com/CVE-2007-3785/index.md)
```

## Sources

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

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