# CVE-2016-3127: Information disclosure in BlackBerry Good Control Server versions earlier than 2.3.53.62

> Remote attackers can access diagnostic logs to steal encryption keys, enabling unauthorized access to customer resources in BlackBerry Good deployments.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w953-99gx-9p86

## What is CVE-2016-3127?

CVE-2016-3127 is a high-severity vulnerability in BlackBerry Good Control Server versions earlier than 2.3.53.62, published on 3 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An information disclosure vulnerability in the logging implementation of BlackBerry Good Control Server versions earlier than 2.3.53.62 allows remote attackers to gain and use logged encryption keys to access certain resources within a customer's Good deployment by gaining access to certain diagnostic log files through either a valid logon or an unrelated compromise of the server.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Blackberry Good Control Server.

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

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

## Is CVE-2016-3127 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-3127 is a high-severity vulnerability in BlackBerry Good Control Server versions earlier than 2.3.53.62, published on 3 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-3127 in the wild and no public exploit code.

Affected product: BlackBerry Good Control Server versions earlier than 2.3.53.62. 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-3127/ (Markdown: https://insights.sbomify.com/CVE-2016-3127/index.md)
```

## Sources

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

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