# CVE-2011-4578: Misconfiguration in n/a

> Local attackers can read or modify files created by acpid event scripts due to an insecure umask setting in the daemon.

- **Severity:** Medium 4.6 (`AV:L/AC:L/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:** Yes
- **Published:** 29 Aug 2012
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-4578, GHSA-cvpp-fv5f-8hch

## What is CVE-2011-4578?

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

### Official description

event.c in acpid (aka acpid2) before 2.0.11 does not have an appropriate umask setting during execution of event-handler scripts, which might allow local users to (1) perform write operations within directories created by a script, or (2) read files created by a script, via standard filesystem system calls.

Weakness: CWE-264

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

It affects 1 product.


Products: Tedfelix Acpid2.

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

Upgrade to a fixed version.

## Is CVE-2011-4578 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2777](https://insights.sbomify.com/CVE-2011-2777/): Privilege escalation in n/a (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-4578 is a medium-severity vulnerability in n/a, published on 29 Aug 2012. 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-4578 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-4578/ (Markdown: https://insights.sbomify.com/CVE-2011-4578/index.md)
```

## Sources

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

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