# CVE-2006-4731: Path traversal in n/a

> Remote attackers can execute arbitrary Perl code via directory traversal in login and admin scripts of SQL-Ledger and LedgerSMB.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-4731, GHSA-r9w9-4622-fw8f

## What is CVE-2006-4731?

CVE-2006-4731 is a medium-severity path traversal vulnerability in n/a, published on 13 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in (1) login.pl and (2) admin.pl in (a) SQL-Ledger before 2.6.19 and (b) LedgerSMB before 1.0.0p1 allow remote attackers to execute arbitrary Perl code via an unspecified terminal parameter value containing ../ (dot dot slash).

## Which versions are affected by CVE-2006-4731?

It affects 2 products.


Products: Dws Systems Inc. Sql-Ledger, Ledgersmb Ledgersmb.

## How do I fix CVE-2006-4731?

Upgrade to a fixed version.

## Is CVE-2006-4731 being exploited?

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

Public exploit code:

- SQL-Ledger 2.6.x/LedgerSMB 1.0 - 'Terminal' Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5372](https://insights.sbomify.com/CVE-2007-5372/): SQL injection in n/a (critical 10.0)
- [CVE-2006-5872](https://insights.sbomify.com/CVE-2006-5872/): Command injection in n/a (high 7.5)
- [CVE-2006-4798](https://insights.sbomify.com/CVE-2006-4798/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4731 and fix it if it is affected.

What it is: CVE-2006-4731 is a medium-severity path traversal vulnerability in n/a, published on 13 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4731 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-2006-4731/ (Markdown: https://insights.sbomify.com/CVE-2006-4731/index.md)
```

## Sources

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

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