# CVE-2003-0401: Information disclosure in n/a

> Remote attackers can obtain sensitive information by requesting a specific template file in Vignette StoryServer.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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-445q-2cxg-hghh

## What is CVE-2003-0401?

CVE-2003-0401 is a medium-severity 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 and Vignette V/5 allows remote attackers to obtain sensitive information via a request for the /vgn/style template.

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

It affects 3 products.


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

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

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

## Is CVE-2003-0401 being exploited?

There is no known exploitation of CVE-2003-0401 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-0402](https://insights.sbomify.com/CVE-2003-0402/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0401 is a medium-severity 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-0401 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-0401/ (Markdown: https://insights.sbomify.com/CVE-2003-0401/index.md)
```

## Sources

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

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