# CVE-2016-3128: A spoofing vulnerability in the Core of BlackBerry Enterprise Server (BES) 12 through 12.5.2 allows remote attackers to enroll an illegitima


- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Jan 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-94c7-grvp-xm27

## What is CVE-2016-3128?

CVE-2016-3128 is a high-severity vulnerability in BES12 versions through 12.5.2, published on 13 Jan 2017. 

### Official description

A 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.

Weakness: CWE-254

## Which versions are affected by CVE-2016-3128?

It affects 1 product.


Products: Blackberry Enterprise Service.

## How do I fix CVE-2016-3128?

No fix has been published for CVE-2016-3128 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-3128 being exploited?

There is no known exploitation of CVE-2016-3128 in the wild and no public exploit code.

## Other vulnerabilities in BES12 versions through 12.5.2

- [CVE-2016-3130](https://insights.sbomify.com/CVE-2016-3130/): Information disclosure in BES12 versions through 12.5.2 (high 8.1)
- [CVE-2017-3894](https://insights.sbomify.com/CVE-2017-3894/): Cross-site scripting in BES12 (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3128 and fix it if it is affected.

What it is: CVE-2016-3128 is a high-severity vulnerability in BES12 versions through 12.5.2, published on 13 Jan 2017. 
Exploitation: There is no known exploitation of CVE-2016-3128 in the wild and no public exploit code.

Affected product: BES12 versions through 12.5.2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-3128/ (Markdown: https://insights.sbomify.com/CVE-2016-3128/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-3128
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-3128
- OSV: https://osv.dev/vulnerability/CVE-2016-3128

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-3128/
Summaries are generated and may contain mistakes; the official description above is the record.