# CVE-2004-1525: Denial of service in n/a

> Remote attackers can crash the Hired Team application by sending a specific status command, causing a denial of service.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xmr3-fcjj-mc3v

## What is CVE-2004-1525?

CVE-2004-1525 is a medium-severity denial of service vulnerability in n/a, published on 19 Feb 2005. It can be exploited over the network, with no action from the victim.

### Official description

Hired Team: Trial 2.0 and earlier and 2.200 allows remote attackers to cause a denial of service (application crash) via the status command.

## Which versions are affected by CVE-2004-1525?


## How do I fix CVE-2004-1525?

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

## Is CVE-2004-1525 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1525 and fix it if it is affected.

What it is: CVE-2004-1525 is a medium-severity denial of service vulnerability in n/a, published on 19 Feb 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-1525 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-2004-1525/ (Markdown: https://insights.sbomify.com/CVE-2004-1525/index.md)
```

## Sources

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

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