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

> Remote attackers can read arbitrary system files via directory traversal in the webMethods Glue Management Console.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-35q3-4p7p-rfwc

## What is CVE-2007-2048?

CVE-2007-2048 is a medium-severity path traversal vulnerability in n/a, published on 16 Apr 2007. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in /console in the Management Console in webMethods Glue 6.5.1 and earlier allows remote attackers to read arbitrary system files via a .. (dot dot) in the resource parameter.

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

It affects 1 product.


Products: Webmethods Glue.

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

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

## Is CVE-2007-2048 being exploited?

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

Public exploit code:

- webMethods Glue 6.5.1 Console - Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2048 is a medium-severity path traversal vulnerability in n/a, published on 16 Apr 2007. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2048 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-2048/ (Markdown: https://insights.sbomify.com/CVE-2007-2048/index.md)
```

## Sources

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

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