dbcve.org
FreeBSDOperating system

CVE-2007-0267

MEDIUM · 6.6 CVSS v2.0 Published 2007-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The ufs_lookup function in the Mac OS X 10.4.8 and FreeBSD 6.1 kernels allows local users to cause a denial of service (kernel panic) and possibly corrupt other filesystems by mounting a crafted UNIX File System (UFS) DMG image that contains a corrupted directory entry (struct direct), related to the ufs_dirbad function. NOTE: a third party states that the FreeBSD issue does not cross privilege boundaries.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability exists in the ufs_lookup function in Mac OS X 10.4.8 and FreeBSD 6.1 kernels where mounting a crafted UFS DMG image containing corrupted directory entries (struct direct) triggers the ufs_dirbad function, causing a kernel panic and potential filesystem corruption.

MitigationAvoid mounting untrusted or unknown UFS DMG images; apply vendor-supplied kernel patches for Mac OS X and FreeBSD to address the ufs_lookup/ufs_dirbad vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreeBSDOperating system
Affected:= 6.1
Mac Os XOperating system
Affected:= 10.4.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:N/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the FreeBSD version
    Run 'uname -a' or check /etc/os-release to confirm the FreeBSD release version
    Affected if The system is running FreeBSD 6.1 specifically
  2. Identify the Mac OS X version
    Run 'sw_vers' or check 'About This Mac' to confirm the Mac OS X version
    Affected if The system is running Mac OS X 10.4.8 specifically
  3. Check if UFS filesystem support is loaded
    On FreeBSD, run 'kldstat | grep ufs' or check /etc/rc.conf for ufs_fsck and ufs_mount_enable settings; On Mac OS X, check if UFS support is present via 'diskutil listFilesystems'
    Affected if UFS filesystem support is enabled or loaded on the system
  4. Verify DMG mounting capability
    Check if the 'hdiutil' command exists (Mac OS X) or if mount_iso9660/dmg support is available (FreeBSD)
    Affected if The system has the ability to mount DMG or similar disk images containing UFS filesystems

The system is affected only if it is running FreeBSD 6.1 or Mac OS X 10.4.8 AND has UFS filesystem support enabled AND can mount DMG or disk images with UFS content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid mounting untrusted or unknown UFS DMG images; apply vendor-supplied kernel patches for Mac OS X and FreeBSD to address the ufs_lookup/ufs_dirbad vulnerability.

Fix this in FreeBSD Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0267 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0267 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data