CVE-2015-8149
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 · uneditedThe LDAP service in Symantec Encryption Management Server (SEMS) 3.3.2 before MP12 allows remote attackers to cause a denial of service (heap memory corruption and service outage) via crafted requests.
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 confidenceThe LDAP service in Symantec Encryption Management Server (SEMS) versions prior to MP12 contains a heap memory corruption vulnerability. Remote attackers can exploit this by sending specially crafted LDAP requests, causing heap memory corruption that leads to service outage and denial of service.
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<= 3.3.2CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the installed SEMS versionAccess the Symantec Encryption Management Server admin console and navigate to Administration > System Health, or run 'sem -v' or 'productversion' from the server CLI if you have direct accessAffected if The version displayed is 3.3.2 or earlier (any version prior to MP12)
-
Verify if LDAP service is enabledIn the SEMS admin console, go to Directory Services > LDAP Settings and confirm if LDAP directory integration is configured and enabled, or check if the LDAP service process is running on the serverAffected if LDAP service is enabled and the server is running (the vulnerability only affects systems with LDAP service active)
-
Check LDAP service network exposureScan the SEMS server for open LDAP ports (TCP 389 for LDAP and TCP 636 for LDAPS) using a port scanner like nmap: 'nmap -p 389,636 <SEMS_IP>' or check local listening ports with 'netstat -an | grep -E ':(389|636)'Affected if LDAP ports 389/636 are listening and accessible from network (remote attackers require network access to send malicious LDAP requests)
-
Confirm the patch levelIn the SEMS admin console, check Administration > Updates or the system information page for the maintenance pack version (MP12 or later indicates the patch is applied)Affected if The system shows a version prior to MP12 (e.g., MP11, MP10, or base 3.3.2)
Your environment is affected if the installed SEMS version is 3.3.2 or earlier AND the LDAP service is enabled and accessible, regardless of whether MP12 patch has been applied.
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 vendor patch (MP12 or later) to SEMS 3.3.2 to remediate the heap corruption vulnerability in the LDAP service. Consider implementing LDAP service rate limiting or network segmentation as additional defensive measures until the patch is applied.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8149 — 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-8149 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