# CVE-2006-4745: Auth bypass in n/a

> Local attackers can bypass authentication and access plaintext data by modifying a file header value in PocketExpense Pro.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7qfh-5rpv-2j99

## What is CVE-2006-4745?

CVE-2006-4745 is a low-severity authentication bypass vulnerability in n/a, published on 13 Sep 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ScaryBear PocketExpense Pro 3.9.1 uses an internally recorded key to protect a data file whose contents are stored in plaintext, which allows local users to disable authentication and access the file by modifying a certain value in the file header.

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

It affects 1 product.


Products: Scarybear Pocketexpense Pro.

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

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

## Is CVE-2006-4745 being exploited?

There is no known exploitation of CVE-2006-4745 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4745 is a low-severity authentication bypass vulnerability in n/a, published on 13 Sep 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4745 in the wild and no public exploit code.

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-4745/ (Markdown: https://insights.sbomify.com/CVE-2006-4745/index.md)
```

## Sources

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

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