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

> Remote attackers can obtain the server's full file path by sending invalid requests to specific DLLs, revealing sensitive system information.

- **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:** 8 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mj84-xc8q-xgp6

## What is CVE-2003-0268?

CVE-2003-0268 is a medium-severity vulnerability in n/a, published on 8 May 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SLWebMail 3 on Windows systems allows remote attackers to identify the full path of the server via invalid requests to DLLs such as WebMailReq.dll, which reveals the path in an error message.

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

It affects 1 product.


Products: Bvrp Software Slwebmail.

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

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

## Is CVE-2003-0268 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0266](https://insights.sbomify.com/CVE-2003-0266/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0267](https://insights.sbomify.com/CVE-2003-0267/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0268 is a medium-severity vulnerability in n/a, published on 8 May 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-0268 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-0268/ (Markdown: https://insights.sbomify.com/CVE-2003-0268/index.md)
```

## Sources

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

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