# CVE-2006-1050: Information disclosure in n/a

> Local attackers can read sensitive payroll data from the Kwik-Pay database file due to insecure file permissions.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h7m2-gw69-h6vr

## What is CVE-2006-1050?

CVE-2006-1050 is a low-severity vulnerability in n/a, published on 7 Mar 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kwik-Pay Payroll 4.2.20, and possibly other versions, stores the KwikPay.mdb database file with insecure permissions, which allows local users to obtain sensitive information such as employment and payment data.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.  NOTE: the vendor has disputed this vulnerability, stating that "The kwikpay.mdb file supplied with kwikpay is a template for the database structure of user databases created by kwikpay and to store a demonstration payroll. It does not contain any sensitive user information.  When a user payroll database is opened, the encryption of the database is checked and if the database is not encrypted, the user is prompted to encrypt the database, but the choice is the customers.

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

It affects 1 product.


Products: Kwik-Pay Kwik-Pay Payroll.

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

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

## Is CVE-2006-1050 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1050 is a low-severity vulnerability in n/a, published on 7 Mar 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-1050 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-1050/ (Markdown: https://insights.sbomify.com/CVE-2006-1050/index.md)
```

## Sources

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

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