# CVE-2004-0099: Security feature bypass in n/a

> A local user can bypass intended access restrictions in FreeBSD by exploiting a flaw in mksnap_ffs that disables security-critical settings.

- **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:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6vw7-q76p-x8g5

## What is CVE-2004-0099?

CVE-2004-0099 is a medium-severity vulnerability in Freebsd Freebsd, published on 1 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

mksnap_ffs in FreeBSD 5.1 and 5.2 only sets the snapshot flag when creating a snapshot for a file system, which causes default values for other flags to be used, possibly disabling security-critical settings and allowing a local user to bypass intended access restrictions.

## Which versions are affected by CVE-2004-0099?

It affects 1 product.


Products: Freebsd Freebsd.

## How do I fix CVE-2004-0099?

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

## Is CVE-2004-0099 being exploited?

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

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0099 and fix it if it is affected.

What it is: CVE-2004-0099 is a medium-severity vulnerability in Freebsd Freebsd, published on 1 Sep 2004. 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-2004-0099 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. 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-2004-0099/ (Markdown: https://insights.sbomify.com/CVE-2004-0099/index.md)
```

## Sources

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

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