# CVE-2003-1333: Other in n/a

> Remote attackers can gain complete control of InterSystems Cache' servers via an unspecified vulnerability in the CSP implementation.

- **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 needed
- **Fix available:** No
- **Published:** 20 Aug 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-34w9-p2mc-gqxq

## What is CVE-2003-1333?

CVE-2003-1333 is a critical vulnerability in n/a, published on 20 Aug 2007. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Cache' Server Page (CSP) implementation in InterSystems Cache' 4.0.3 through 5.0.5 allows remote attackers to "gain complete control" of a server.

## Which versions are affected by CVE-2003-1333?

It affects 1 product.


Products: Intersystems Cache Database.

## How do I fix CVE-2003-1333?

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

## Is CVE-2003-1333 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0497](https://insights.sbomify.com/CVE-2003-0497/): Privilege escalation in n/a (high 7.2)
- [CVE-2003-0498](https://insights.sbomify.com/CVE-2003-0498/): Code injection in n/a (high 7.2)
- [CVE-2007-0437](https://insights.sbomify.com/CVE-2007-0437/): Cross-site scripting in n/a (low 3.5)
- [CVE-2007-4427](https://insights.sbomify.com/CVE-2007-4427/): Business logic in n/a (low 3.5)
- [CVE-2004-2684](https://insights.sbomify.com/CVE-2004-2684/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1333 and fix it if it is affected.

What it is: CVE-2003-1333 is a critical vulnerability in n/a, published on 20 Aug 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-1333 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-2003-1333/ (Markdown: https://insights.sbomify.com/CVE-2003-1333/index.md)
```

## Sources

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

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