dbcve.org
FedoraOperating system · Fedoraproject

CVE-2007-1321

HIGH · 7.2 CVSS v2.0 Published 2007-10-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Integer signedness error in the NE2000 emulator in QEMU 0.8.2, as used in Xen and possibly other products, allows local users to trigger a heap-based buffer overflow via certain register values that bypass sanity checks, aka QEMU NE2000 "receive" integer signedness error. NOTE: this identifier was inadvertently used by some sources to cover multiple issues that were labeled "NE2000 network driver and the socket code," but separate identifiers have been created for the individual vulnerabilities since there are sometimes different fixes; see CVE-2007-5729 and CVE-2007-5730.

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

Integer signedness error in QEMU's NE2000 network card emulator allows local users to trigger a heap-based buffer overflow by providing register values that bypass sanity checks. The vulnerability exists in the emulator's receive path where signed/unsigned integer comparisons fail to properly validate input, potentially allowing memory corruption.

MitigationUpdate QEMU to a version with the signedness check fixes in the NE2000 emulator (related fixes addressed in CVE-2007-5729 and CVE-2007-5730). For systems using Xen with QEMU, apply Xen patches. As a local privilege escalation vector, restrict unauthorized local access to the virtualization host.

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
FedoraOperating system
Affected:= 7
Debian LinuxOperating system
Affected:= 3.1= 4.0
QemuApplication
Affected:= 0.8.2
Fedora CoreOperating system
Affected:= 6

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
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/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 QEMU installation and version
    Run 'qemu --version' or check your package manager (rpm -q qemu or dpkg -l qemu) to find the installed QEMU version
    Affected if The installed version is 0.8.2, or the distribution is Fedora 7, Fedora Core 6, or Debian 3.1/4.0 with bundled QEMU at the vulnerable version
  2. Check for running QEMU processes with NE2000 emulation
    Examine running processes and their command-line arguments for NE2000 network device usage: 'ps aux | grep -i qemu' and look for '-net nic,model=ne2k_pci' or similar NE2000 configuration
    Affected if QEMU is running with NE2000 (ne2k_pci or ne2k_isa) network device emulation enabled
  3. Verify QEMU binary location and associated packages
    Use 'which qemu' or 'rpm -qa | grep -i qemu' (RHEL/Fedora) or 'dpkg -l | grep -i qemu' (Debian) to list all QEMU-related packages
    Affected if Any installed QEMU package version matches the affected versions listed (0.8.2 or distribution versions known to include the vulnerable code)
  4. Check for Xen with QEMU emulator (if applicable)
    On Xen systems, identify if QEMU is used for device emulation: 'xm list' to see domains and check for HVM domains that use QEMU for NE2000 emulation
    Affected if Running Xen with HVM domains utilizing QEMU for hardware emulation with NE2000 network device

You are affected if QEMU version 0.8.2 (or the specific Fedora/Debian versions listed) is installed and NE2000 network card emulation is in use.

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

Update QEMU to a version with the signedness check fixes in the NE2000 emulator (related fixes addressed in CVE-2007-5729 and CVE-2007-5730). For systems using Xen with QEMU, apply Xen patches. As a local privilege escalation vector, restrict unauthorized local access to the virtualization host.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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