# CVE-2007-2407: Missing authorization in n/a

> Authenticated users can exceed disk quotas on Mac OS X when Windows file sharing is enabled, allowing unauthorized storage consumption.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jv6m-h4m5-f426, MINI-pv52-h7c3-ghxg

## What is CVE-2007-2407?

CVE-2007-2407 is a medium-severity missing authorization vulnerability in n/a, published on 3 Aug 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Samba server on Apple Mac OS X 10.3.9 and 10.4.10, when Windows file sharing is enabled, does not enforce disk quotas after dropping privileges, which allows remote authenticated users to use disk space in excess of quota.

## Which versions are affected by CVE-2007-2407?

It affects 1 product.


Products: Samba Samba Server.

## How do I fix CVE-2007-2407?

Apply the vendor's patch.

## Is CVE-2007-2407 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2407 and fix it if it is affected.

What it is: CVE-2007-2407 is a medium-severity missing authorization vulnerability in n/a, published on 3 Aug 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2407 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-2007-2407/ (Markdown: https://insights.sbomify.com/CVE-2007-2407/index.md)
```

## Sources

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

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