# CVE-2002-0462: Denial of service in n/a

> Remote attackers can cause denial of service or leak web server paths via a large displayBegin parameter in the Big Sam guestbook module.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7j7c-6wrr-cv8r

## What is CVE-2002-0462?

CVE-2002-0462 is a medium-severity denial of service vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

bigsam_guestbook.php for Big Sam (Built-In Guestbook Stand-Alone Module) 1.1.08 and earlier allows remote attackers to cause a denial of service (CPU consumption) or obtain the absolute path of the web server via a displayBegin parameter with a very large number, which leaks the web path in an error message when PHP safe_mode is enabled, or consumes resources when safe_mode is not enabled.

## Which versions are affected by CVE-2002-0462?

It affects 1 product.


Products: Big Sam Big Sam.

## How do I fix CVE-2002-0462?

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

## Is CVE-2002-0462 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0462 and fix it if it is affected.

What it is: CVE-2002-0462 is a medium-severity denial of service vulnerability in n/a, published on 2 Apr 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-2002-0462 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-2002-0462/ (Markdown: https://insights.sbomify.com/CVE-2002-0462/index.md)
```

## Sources

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

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