# CVE-2003-0405: Code injection in n/a

> Remote attackers can execute arbitrary TCL code in Vignette StoryServer via crafted HTTP requests, leading to full system compromise.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/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:** 11 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-64vq-wgg6-6rp5

## What is CVE-2003-0405?

CVE-2003-0405 is a medium-severity code injection vulnerability in n/a, published on 11 Jun 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vignette StoryServer 5 and Vignette V/6 allows remote attackers to execute arbitrary TCL code via (1) an HTTP query or cookie which is processed in the NEEDS command, or (2) an HTTP Referrer that is processed in the VALID_PATHS command.

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

It affects 3 products.


Products: Vignette Content Suite, Vignette Storyserver, Vignette Vignette.

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

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

## Is CVE-2003-0405 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0398](https://insights.sbomify.com/CVE-2003-0398/): Code injection in n/a (high 7.5)
- [CVE-2003-0403](https://insights.sbomify.com/CVE-2003-0403/): Missing authorization in n/a (high 7.5)
- [CVE-2003-0399](https://insights.sbomify.com/CVE-2003-0399/): Auth bypass in n/a (medium 6.4)
- [CVE-2003-0400](https://insights.sbomify.com/CVE-2003-0400/): Information disclosure in n/a (medium 5.0)
- [CVE-2003-0401](https://insights.sbomify.com/CVE-2003-0401/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0405 is a medium-severity code injection vulnerability in n/a, published on 11 Jun 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0405 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-0405/ (Markdown: https://insights.sbomify.com/CVE-2003-0405/index.md)
```

## Sources

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

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