CVE-2007-6679
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 Administrative Console in IBM WebSphere Application Server 6.1 before Fix Pack 13 has unknown impact and attack vectors, related to "security concerns with monitor role users." NOTE: it was later reported that 6.0.2 before Fix Pack 25 is also affected.
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 confidenceVulnerability in IBM WebSphere Application Server Administrative Console allows users with 'monitor' role to perform unauthorized actions or access sensitive functions. The exact mechanism is unspecified but relates to improper authorization enforcement for monitor role users in the console.
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<= 6.0.2.24= 6.1= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.1.0.5= 6.1.0.7= 6.1.0.9= 6.1.0.11CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify WebSphere Application Server versionRun 'about' command in the wsadmin scripting tool or check the installation directory for version.info. Alternatively, log into the admin console and view the runtime information under 'Servers > Server Types > WebSphere application servers' or check the 'About This Installation' link in the console.Affected if The installed version is 6.0.2.24 or earlier, or exactly 6.1, 6.1.0.1, 6.1.0.2, 6.1.0.3, 6.1.0.5, 6.1.0.7, 6.1.0.9, or 6.1.0.11.
-
Verify admin console is enabledCheck if the Administrative Console is accessible by attempting to reach the console URL (typically https://hostname:9043/ibm/console) or check the console enabled property in the deployment manager configuration.Affected if The admin console is accessible and active.
-
Check for monitor role assignmentsIn the admin console, navigate to 'Users and Groups > Administrative user roles' or check the security.xml configuration file for users or groups assigned the 'monitor' role.Affected if Any user or group is assigned the monitor role in the WebSphere security configuration.
-
Review console authorization settingsExamine the console security settings under 'Security > Global security' and verify the role-to-user mappings for the console. Check if monitor role has been granted any administrative functionality beyond read-only access.Affected if Monitor role users can access administrative functions beyond monitoring capabilities.
You are affected if your WebSphere version matches the affected list (6.0.2.24 or earlier, or 6.1.x versions up to 6.1.0.11) AND the admin console is active with users assigned the monitor role.
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.
dbcve · scopedApply IBM WebSphere Application Server Fix Pack 13 for version 6.1 or Fix Pack 25 for version 6.0.2, or later stable releases, to address the monitor role authorization issue.
WebSphere 6.1: Fix Pack 13 or later; WebSphere 6.0.2: Fix Pack 25 or later
- Identify your current WebSphere Application Server exact version (6.0.2.x or 6.1.x) and fix pack level
- If running WebSphere 6.1.x: Upgrade to Fix Pack 13 or later to resolve the monitor role security vulnerability
- If running WebSphere 6.0.2.x: Upgrade to Fix Pack 25 or later to resolve the vulnerability
- After applying the fix pack, verify that monitor role users no longer have elevated administrative privileges
- Test the Administrative Console functionality after the upgrade to ensure normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6679 — 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-6679 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