dbcve.org
SambaApplication

CVE-2007-0452

MEDIUM · 6.8 CVSS v2.0 Published 2007-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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
smbd in Samba 3.0.6 through 3.0.23d allows remote authenticated users to cause a denial of service (memory and CPU exhaustion) by renaming a file in a way that prevents a request from being removed from the deferred open queue, which triggers an infinite loop.

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 · high confidence

The vulnerability exists in smbd's deferred open queue handling mechanism. When an authenticated remote user renames a file in a specific manner that prevents a request from being properly removed from the deferred open queue, it triggers an infinite loop. This causes memory allocation and CPU exhaustion, resulting in denial of service.

MitigationUpgrade to Samba 3.0.24 or later, which contains the fix for this vulnerability. Alternatively, apply the vendor patch if upgrading is not immediately feasible.

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
SambaApplication
Affected:= 3.0.6= 3.0.7= 3.0.8= 3.0.9= 3.0.10= 3.0.11= 3.0.12= 3.0.13= 3.0.14a= 3.0.20= 3.0.20a= 3.0.20b

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
Network
Complexity
Low
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:S/C:N/I:N/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. Confirm Samba smbd is running
    Run 'ps aux | grep smbd' or check if ports 139/445 are listening (e.g., 'netstat -tlnp | grep -E "(139|445)"')
    Affected if smbd process is active and listening on network ports
  2. Identify the installed Samba version
    Run 'smbd --version' or check your package manager (e.g., 'rpm -q samba' for RHEL, 'dpkg -l samba' for Debian)
    Affected if Version matches 3.0.6 through 3.0.14a, 3.0.20, 3.0.20a, or 3.0.20b
  3. Verify smbd is exposed to remote network access
    Check smb.conf for 'bind interfaces only = no' and inspect listening interfaces; examine firewall rules to confirm ports 139/445 are accessible from network
    Affected if smbd binds to non-localhost interfaces and is reachable from remote clients
  4. Confirm remote user authentication is enabled
    Review smb.conf for 'security = share' or 'security = user' settings, and check that user accounts exist in the Samba password database (pdbedit -L or smbpasswd -L)
    Affected if Remote authenticated users can connect to the smbd service

You are affected if you are running an affected Samba version (3.0.6-3.0.14a, 3.0.20, 3.0.20a, or 3.0.20b) with smbd accessible to remote authenticated users on the network.

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

Upgrade to Samba 3.0.24 or later, which contains the fix for this vulnerability. Alternatively, apply the vendor patch if upgrading is not immediately feasible.

Fix this in Samba Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0452 — 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-0452 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