# CVE-2011-1159: Denial of service in n/a

> Local attackers can cause the acpid daemon to hang by connecting to its socket without reading data, resulting in a denial of service.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2011
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2011-1159, GHSA-vp73-h36r-mx65

## What is CVE-2011-1159?

CVE-2011-1159 is a low-severity denial of service vulnerability in n/a, published on 5 Oct 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

acpid.c in acpid before 2.0.9 does not properly handle a situation in which a process has connected to acpid.socket but is not reading any data, which allows local users to cause a denial of service (daemon hang) via a crafted application that performs a connect system call but no read system calls.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Tedfelix Acpid.

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

Upgrade to a fixed version.

## Is CVE-2011-1159 being exploited?

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

Public exploit code:

- acpid 1.0.x - Multiple Local Denial of Service Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1159 is a low-severity denial of service vulnerability in n/a, published on 5 Oct 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-1159 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-2011-1159/ (Markdown: https://insights.sbomify.com/CVE-2011-1159/index.md)
```

## Sources

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

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