# CVE-2008-1127: Memory corruption in n/a

> Remote authenticated users can execute arbitrary code via format string specifiers in the username when a character is killed.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hhq7-6g2p-f5h6

## What is CVE-2008-1127?

CVE-2008-1127 is a medium-severity memory corruption vulnerability in n/a, published on 3 Mar 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Format string vulnerability in the cryactio function in Crysis 1.1.1.5879 allows remote authenticated users to execute arbitrary code via format string specifiers in the user name, which is triggered when the game character is killed.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2008-1127?

It affects 1 product.


Products: Crytek Crysis.

## How do I fix CVE-2008-1127?

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

## Is CVE-2008-1127 being exploited?

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

Public exploit code:

- Crysis 1.1.1.5879 - Remote Format String Denial of Service (PoC) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1127 and fix it if it is affected.

What it is: CVE-2008-1127 is a medium-severity memory corruption vulnerability in n/a, published on 3 Mar 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-1127 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-2008-1127/ (Markdown: https://insights.sbomify.com/CVE-2008-1127/index.md)
```

## Sources

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

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