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

> Remote attackers can overwrite, read, or execute arbitrary files via insecure ActiveX methods in SAP GUI, requiring user interaction.

- **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:** 16 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mh5m-5r69-7g2f

## What is CVE-2008-4830?

CVE-2008-4830 is a critical path traversal vulnerability in n/a, published on 16 Apr 2009. 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

Insecure method vulnerability in the KWEdit ActiveX control in SAP GUI 6.40 Patch 29 (KWEDIT.DLL 6400.1.1.41) and 7.10 Patch 5 (KWEDIT.DLL 7100.1.1.43) allows remote attackers to (1) overwrite arbitrary files via the SaveDocumentAs method or (2) read or execute arbitrary files via the OpenDocument method.

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

It affects 1 product.


Products: Sap Sap Gui.

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

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

## Is CVE-2008-4830 being exploited?

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

Public exploit code:

- EnjoySAP SAP GUI ActiveX Control Arbitrary File Download (metasploit)
- EnjoySAP SAP GUI - ActiveX Control Arbitrary File Download (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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