# CVE-2009-1601: Missing authorization in n/a

> Local users can bypass access restrictions to read or write files in the current working directory due to improper ownership settings in the ClamAV milter init script.

- **Severity:** Medium 6.8 (`AV:L/AC:L/Au:S/C:C/I:C/A:C`)
- **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:** 11 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-646v-76hm-m37p

## What is CVE-2009-1601?

CVE-2009-1601 is a medium-severity missing authorization vulnerability in n/a, published on 11 May 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Ubuntu clamav-milter.init script in clamav-milter before 0.95.1+dfsg-1ubuntu1.2 in Ubuntu 9.04 sets the ownership of the current working directory to the clamav account, which might allow local users to bypass intended access restrictions via read or write operations involving this directory.

Weakness: CWE-264

## Which versions are affected by CVE-2009-1601?

It affects 1 product.


Products: Ubuntu Linux.

## How do I fix CVE-2009-1601?

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

## Is CVE-2009-1601 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-4306](https://insights.sbomify.com/CVE-2008-4306/): Memory corruption in n/a (critical 9.3)
- [CVE-2008-6792](https://insights.sbomify.com/CVE-2008-6792/): Weak cryptography in n/a (medium 5.0)
- [CVE-2008-2285](https://insights.sbomify.com/CVE-2008-2285/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1601 and fix it if it is affected.

What it is: CVE-2009-1601 is a medium-severity missing authorization vulnerability in n/a, published on 11 May 2009. 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-2009-1601 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-2009-1601/ (Markdown: https://insights.sbomify.com/CVE-2009-1601/index.md)
```

## Sources

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

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