# CVE-2005-4829: Other in n/a

> VirtueMart fails to properly handle errors when users are forbidden from reading pages, potentially allowing unauthorized access or information disclosure.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 26 Feb 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3rrr-cqqf-5xqm

## What is CVE-2005-4829?

CVE-2005-4829 is a critical vulnerability in n/a, published on 26 Feb 2007. It can be exploited over the network.

### Official description

VirtueMart before 1.0.1 does not properly handle errors when a user is forbidden to read a requested page, which has unknown impact and remote attack vectors.

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

It affects 1 product.


Products: Virtuemart Virtuemart.

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

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

## Is CVE-2005-4829 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4430](https://insights.sbomify.com/CVE-2009-4430/): SQL injection in n/a (high 7.5)
- [CVE-2007-5563](https://insights.sbomify.com/CVE-2007-5563/): Code injection in n/a (high 7.5)
- [CVE-2006-6945](https://insights.sbomify.com/CVE-2006-6945/): SQL injection in n/a (high 7.5)
- [CVE-2016-10379](https://insights.sbomify.com/CVE-2016-10379/): SQL injection in n/a (high 7.2)
- [CVE-2008-7204](https://insights.sbomify.com/CVE-2008-7204/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4829 is a critical vulnerability in n/a, published on 26 Feb 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2005-4829 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-2005-4829/ (Markdown: https://insights.sbomify.com/CVE-2005-4829/index.md)
```

## Sources

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

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