# CVE-2006-5033: Denial of service in n/a

> Remote attackers can cause a denial of service in vCAP via the session parameter in StoresAndCalendarsList.cgi.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-57p6-859p-jwq8

## What is CVE-2006-5033?

CVE-2006-5033 is a medium-severity denial of service vulnerability in n/a, published on 27 Sep 2006. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in StoresAndCalendarsList.cgi in Paul Smith Computer Services vCAP 1.9.0 Beta and earlier allows remote attackers to cause a denial of service via the session parameter, possibly related to format string specifiers or malformed URL encoding.

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

It affects 1 product.


Products: Paul Smith Computer Services Vcap.

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

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

## Is CVE-2006-5033 being exploited?

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

Public exploit code:

- Paul Smith Computer Services VCAP Calendar Server 1.9 - Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-5034](https://insights.sbomify.com/CVE-2006-5034/): Path traversal in n/a (medium 5.0)
- [CVE-2006-5035](https://insights.sbomify.com/CVE-2006-5035/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5033 is a medium-severity denial of service vulnerability in n/a, published on 27 Sep 2006. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5033 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-5033/ (Markdown: https://insights.sbomify.com/CVE-2006-5033/index.md)
```

## Sources

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

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