# CVE-2008-1725: Path traversal in n/a

> Remote attackers can overwrite arbitrary files via the unsafe WriteOFXDataFile method in the IBiz E-Banking Integrator ActiveX control.

- **Severity:** Critical 9.0 (`AV:N/AC:M/Au:N/C:P/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:** 11 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7chf-fr3c-mjmm

## What is CVE-2008-1725?

CVE-2008-1725 is a critical path traversal vulnerability in n/a, published on 11 Apr 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

The IBizEBank.FIProfile.1 ActiveX control in fiprofile20.ocx in IBiz E-Banking Integrator (formerly IBiz OFX Integrator) 2.0.2932 exposes the unsafe WriteOFXDataFile method, which allows remote attackers to overwrite arbitrary files via a full pathname in the argument.  NOTE: some of these details are obtained from third party information.

## Which versions are affected by CVE-2008-1725?

It affects 1 product.


Products: Nsoftware Ibiz E-Banking Integrator.

## How do I fix CVE-2008-1725?

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

## Is CVE-2008-1725 being exploited?

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

Public exploit code:

- IBiz E-Banking Integrator 2.0 - ActiveX Edition Insecure Method (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1725 and fix it if it is affected.

What it is: CVE-2008-1725 is a critical path traversal vulnerability in n/a, published on 11 Apr 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-2008-1725 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-2008-1725/ (Markdown: https://insights.sbomify.com/CVE-2008-1725/index.md)
```

## Sources

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

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