CVE-2014-9921
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 · uneditedInformation disclosure vulnerability in McAfee (now Intel Security) Cloud Analysis and Deconstructive Services (CADS) 1.0.0.3x, 1.0.0.4d and earlier allows remote unauthenticated users to view, add, and remove users via a configuration error.
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 confidenceA configuration error in McAfee Cloud Analysis and Deconstructive Services (CADS) allows remote unauthenticated attackers to access the user management interface. Due to this misconfiguration, attackers can view, add, and remove user accounts without any authentication, effectively granting full administrative access to the system.
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<= 1.0.0.4d= 1.0.0.3CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 CADS installation and versionLocate the McAfee CADS installation directory and check the version file or product information. Common locations may include /opt/mcafee/cads/ or registry entries on Windows installations. Look for version manifests, about dialogs, or product info files.Affected if Installed version is 1.0.0.3 or 1.0.0.4d or earlier (check your discovered version against these affected ranges)
-
Test user management interface accessibilityAttempt to access the CADS user management interface URL without providing any authentication credentials. This is typically found at a path like /useradmin, /admin/users, or /cads/user management endpoints. Use a web browser or curl command with no authentication headers.Affected if The interface loads and displays user account information, add user forms, or administrative panels without redirecting to a login page or returning an authentication error
-
Verify authentication enforcement on user endpointsInspect the CADS web server or application configuration files (such as web.xml, application.properties, or similar) to verify that authentication is required for all user management paths. Check for security constraint definitions and auth-constraint settings.Affected if Configuration files show missing or disabled authentication requirements for user management endpoints, or permit-anonymous-access is set to true for these paths
-
Check for exposed user account dataWith no authentication, attempt to enumerate or list user accounts through the CADS interface. Attempt to access any API endpoints that return user data, roles, or permissions without credentials.Affected if User account lists, role information, or permission data is returned successfully without any authentication tokens or credentials
A user is affected if CADS version is 1.0.0.3 or 1.0.0.4d or earlier AND the user management interface is accessible without authentication credentials.
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 dataFix the authentication configuration to enforce proper authentication on all user management endpoints, and apply any available vendor patches for affected CADS versions (1.0.0.3x, 1.0.0.4d and earlier).
- 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-2014-9921 — 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-2014-9921 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