CVE-2008-2707
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 · uneditedUnspecified vulnerability in the e1000g driver in Sun Solaris 10 and OpenSolaris before snv_93 allows remote attackers to cause a denial of service (network connectivity loss) via unknown vectors.
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 confidenceThe e1000g network driver in Sun Solaris 10 and OpenSolaris prior to snv_93 contains an unspecified vulnerability that allows remote attackers to cause network connectivity loss, effectively creating a denial of service condition. The vulnerability is in a kernel-level network driver and can be exploited remotely via unknown vectors.
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= 82571= 82572CVSS 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
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check the Solaris versionRun 'uname -a' or inspect '/etc/release' to identify the OS version. For OpenSolaris, check if the version is prior to snv_93.Affected if The system runs Solaris 10 (any update) or OpenSolaris prior to snv_93
-
Identify if e1000g driver is loadedRun 'modinfo | grep e1000g' or check 'dmesg' output for e1000g driver presence.Affected if The e1000g driver is loaded and active on the system
-
Verify the network hardwareRun 'prtconf -v' or 'dmesg | grep -i "82571\|82572"' to identify the installed Intel network controller model.Affected if The system has an Intel 82571 or 82572 network interface controller installed and using the e1000g driver
-
Confirm the driver version if availableRun 'modinfo -c e1000g' or check driver metadata files in /kernel/drv/ for version information if accessible.Affected if The e1000g driver version matches the vulnerable version present in Solaris 10 or pre-snv_93 OpenSolaris
A user is affected if they are running Solaris 10 or OpenSolaris prior to snv_93 with an Intel 82571 or 82572 network controller using the e1000g driver.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the Solaris 10 patch bundle or upgrade OpenSolaris to snv_93 or later to obtain the patched e1000g driver. Alternatively, consider network segmentation or firewall rules to limit exposure to untrusted networks until the patch can be applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-2707 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-2707 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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