# CVE-2011-5033: Memory corruption in n/a

> Local attackers can crash the ConfigServer Security & Firewall on DirectAdmin servers by providing a long string in the admin.list file.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Dec 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rf2x-23jg-qfw8

## What is CVE-2011-5033?

CVE-2011-5033 is a medium-severity memory corruption vulnerability in n/a, published on 29 Dec 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based buffer overflow in CFS.c in ConfigServer Security & Firewall (CSF) before 5.43, when running on a DirectAdmin server, allows local users to cause a denial of service (crash) via a long string in an admin.list file.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2011-5033?

It affects 1 product.


Products: Configserver Configserver Security Firewall.

## How do I fix CVE-2011-5033?

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

## Is CVE-2011-5033 being exploited?

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

Public exploit code:

- CSF Firewall - Buffer Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5033 and fix it if it is affected.

What it is: CVE-2011-5033 is a medium-severity memory corruption vulnerability in n/a, published on 29 Dec 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-5033 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-2011-5033/ (Markdown: https://insights.sbomify.com/CVE-2011-5033/index.md)
```

## Sources

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

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