CVE-2015-0546
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 · uneditedEMC Unified Infrastructure Manager/Provisioning (UIM/P) 4.1 allows remote attackers to bypass LDAP authentication by providing a valid account name.
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 confidenceEMC Unified Infrastructure Manager/Provisioning (UIM/P) 4.1 contains a critical authentication bypass vulnerability where remote attackers can bypass LDAP authentication simply by providing a valid account name. This allows unauthenticated attackers to gain unauthorized access to the system without needing to provide valid credentials.
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= 4.1CVSS 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.
-
Confirm EMC UIM/P is installedLocate the EMC Unified Infrastructure Manager or Provisioning installation directory, or check system inventory/Software list for 'EMC Unified Infrastructure Manager' or 'UIM'Affected if The product is present on the system
-
Verify the installed version is 4.1Check the version of EMC UIM/P by reviewing the software's about page, version file, or running the product's version command. Compare against the affected version range: 4.1Affected if The installed version is exactly 4.1
-
Confirm LDAP authentication is configuredAccess the UIM/P administrative console and review the authentication settings or security configuration to determine if LDAP-based authentication is enabledAffected if LDAP authentication is enabled and in use
-
Review authentication logs for anomaliesExamine UIM/P authentication and access logs for failed login attempts that do not require password verification, or for successful logins using only an account name without password validationAffected if Log entries show successful authentications without proper credential validation
-
Check for unauthorized user accountsAudit the list of configured LDAP users or groups in UIM/P to identify any accounts that were added without proper administrative approvalAffected if Unexpected accounts or groups exist in the LDAP configuration
A system is affected if it runs EMC Unified Infrastructure Manager/Provisioning version 4.1 with LDAP authentication enabled, allowing attackers to bypass authentication by supplying only a valid account name.
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 vendor-supplied security patches or updates for EMC UIM/P 4.1 immediately. Until patching is possible, implement strict network access controls, disable unnecessary LDAP bindings, and monitor for suspicious authentication attempts using valid account names.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0546 — 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-2015-0546 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