# CVE-2005-0280: Other in n/a

> Remote attackers can crash the server or execute arbitrary code via format string vulnerabilities in Soldner Secret Wars.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 10 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6fw2-8jqq-27x2

## What is CVE-2005-0280?

CVE-2005-0280 is a high-severity vulnerability in n/a, published on 10 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in Soldner Secret Wars 30830 and earlier allows remote attackers to cause a denial of service (server crash) and possibly execute arbitrary code via format string specifiers in a message.

## Which versions are affected by CVE-2005-0280?

It affects 1 product.


Products: Jowood Productions Soldner Secret Wars.

## How do I fix CVE-2005-0280?

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

## Is CVE-2005-0280 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0280 exists.

Public exploit code:

- SOLDNER Secret Wars 30830 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0279](https://insights.sbomify.com/CVE-2005-0279/): Denial of service in n/a (medium 5.0)
- [CVE-2005-0281](https://insights.sbomify.com/CVE-2005-0281/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0280 and fix it if it is affected.

What it is: CVE-2005-0280 is a high-severity vulnerability in n/a, published on 10 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0280 exists.

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-2005-0280/ (Markdown: https://insights.sbomify.com/CVE-2005-0280/index.md)
```

## Sources

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

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