# CVE-2005-0409: Missing authorization in n/a

> Remote attackers can upload credit card data and access sensitive file paths due to missing authorization checks in CitrusDB.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** No
- **Published:** 16 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6gw3-9jpp-7crr

## What is CVE-2005-0409?

CVE-2005-0409 is a medium-severity missing authorization vulnerability in n/a, published on 16 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CitrusDB 0.3.6 and earlier does not verify authorization for the (1) importcc.php and (2) uploadcc.php, which allows remote attackers to upload credit card data and obtain sensitive information such as the pathnames for temporary files that store credit card data, and facilitates the exploitation of other vulnerabilities.

## Which versions are affected by CVE-2005-0409?

It affects 1 product.


Products: Citrusdb Citrusdb.

## How do I fix CVE-2005-0409?

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

## Is CVE-2005-0409 being exploited?

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

Public exploit code:

- CitrusDB 0.3.6 - 'importcc.php' Arbitrary Database Injection (exploitdb)
- CitrusDB 0.3.6 - 'uploadcc.php' Arbitrary Database Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0408](https://insights.sbomify.com/CVE-2005-0408/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2005-0411](https://insights.sbomify.com/CVE-2005-0411/): Path traversal in n/a (high 7.5)
- [CVE-2005-0410](https://insights.sbomify.com/CVE-2005-0410/): SQL injection in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0409 and fix it if it is affected.

What it is: CVE-2005-0409 is a medium-severity missing authorization vulnerability in n/a, published on 16 Feb 2005. 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-2005-0409 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-2005-0409/ (Markdown: https://insights.sbomify.com/CVE-2005-0409/index.md)
```

## Sources

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

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