CVE-2007-1346
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 ipmitool for Sun Fire X2100M2 and X2200M2 allows local users to gain privileges and reset or turn off the server.
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 confidenceThis is a local privilege escalation vulnerability in ipmitool affecting Sun Fire X2100M2 and X2200M2 servers. Local users can exploit unspecified vulnerabilities in the ipmitool implementation to gain elevated privileges, allowing them to reset or power off the server.
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= x2100m2= x2200m2CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:S/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 checksWork through these to decide whether this CVE applies to you.
-
Identify server modelRun 'dmidecode -s system-product-name' or check /proc/cpuinfo for Sun Fire hardware identifierAffected if System is not a Sun Fire X2100M2 or X2200M2 (these are the only affected models)
-
Verify ipmitool installationRun 'which ipmitool' or check if /usr/bin/ipmitool or /sbin/ipmitool existsAffected if ipmitool is not installed on the system
-
Check ipmitool binary permissionsRun 'ls -la $(which ipmitool)' to view owner, group, and world execute permissionsAffected if The binary is world-writable or owned by a non-root user with weak group permissions
-
Identify ipmitool usersRun 'ls -la /usr/bin/ipmitool /etc/ipmi* 2>/dev/null' and check group membership of users in the 'ipmi' or 'wheel' groupsAffected if Non-privileged users have access to ipmitool or belong to IPMI management groups
-
Check for existing privilege escalation indicatorsReview system logs in /var/log/messages and /var/log/secure for ipmitool commands run by non-root users, and check 'ls -la /var/log/ipmi*' if availableAffected if Non-root users have executed ipmitool commands that could indicate exploitation
The system is affected only if it is a Sun Fire X2100M2 or X2200M2 server with ipmitool installed and accessible to untrusted local users.
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 dataRestrict local system access to trusted users only, ensure restrictive file permissions on ipmitool binaries and configuration files, and verify if vendor patches for ipmitool are available for these specific Sun Fire models.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1346 — 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-2007-1346 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