CVE-2016-3128
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 · uneditedA spoofing vulnerability in the Core of BlackBerry Enterprise Server (BES) 12 through 12.5.2 allows remote attackers to enroll an illegitimate device to the BES, gain access to device parameters for the BES, or send false information to the BES by gaining access to specific information about a device that was legitimately enrolled on the BES.
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 spoofing vulnerability in the core enrollment mechanism of BlackBerry Enterprise Server 12 through 12.5.2 allows remote attackers to impersonate legitimately enrolled devices by obtaining specific device information, enabling unauthorized device enrollment and manipulation of BES device data.
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= 12.0.0= 12.0.1= 12.1.0= 12.2.0= 12.2.1= 12.3.0= 12.3.1= 12.4.0= 12.4.1= 12.5.0a= 12.5.1= 12.5.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
- Low
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
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 BES versionLocate the installed BlackBerry Enterprise Server version through the BES Admin console, installation directory, or system information. Common locations include the BES console dashboard or Windows Programs and Features.Affected if The installed version matches 12.0.0, 12.0.1, 12.1.0, 12.2.0, 12.2.1, 12.3.0, 12.3.1, 12.4.0, 12.4.1, 12.5.0a, 12.5.1, or 12.5.2.
-
Verify device enrollment is enabledAccess the BES admin console and check the device enrollment settings under the Enterprise Mobility Management or Device Services configuration section. Confirm whether the core enrollment mechanism allows new device registrations.Affected if Device enrollment functionality is active and accessible to external network traffic.
-
Review enrollment logs for unauthorized activityExamine BES enrollment and device management logs for entries showing enrollment attempts from unexpected device identifiers, repeated enrollment requests, or device records that cannot be attributed to known users. Check logs in the BES data directory or through the administration console log viewer.Affected if Logs contain enrollment records with device identifiers not matching legitimate enrolled devices, or show enrollment activity from unexpected sources.
-
Audit existing device enrollmentsExport the current list of enrolled devices from the BES console and verify each entry against known, legitimate device records. Look for duplicate device IDs, unexpected device types, or devices enrolled outside normal enrollment workflows.Affected if The device inventory contains enrollments that cannot be verified against documented, legitimate device deployments.
You are affected if your BES 12 installation runs any version from 12.0.0 through 12.5.2 AND has device enrollment enabled, with any signs of unauthorized or suspicious enrollment activity in logs or device inventory.
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 available vendor patches for BES 12.x and review device enrollment workflows for additional authentication controls; consider network segmentation to limit exposure of device enrollment traffic.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3128 — 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-2016-3128 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