# CVE-2003-1462: Denial of service in n/a

> Remote attackers can cause denial of service via disk consumption by creating subdirectories for non-existent surveys in mod_survey.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/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:** 24 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vcxw-6r9g-hhw5

## What is CVE-2003-1462?

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

### Official description

mod_survey 3.0.0 through 3.0.15-pre6 does not check whether a survey exists before creating a subdirectory for it, which allows remote attackers to cause a denial of service (disk consumption and possible crash).

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

It affects 1 product.


Products: Mod Survey Mod Survey.

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

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

## Is CVE-2003-1462 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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