# CVE-2016-3129: Command injection in BlackBerry GEMS versions 2.1.5.3 to 2.2.22.25

> Remote attackers can execute commands on the Karaf shell to gain local administrator rights on the BlackBerry GEMS server.

- **Severity:** Medium 6.6 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-53j4-j69m-55qw

## What is CVE-2016-3129?

CVE-2016-3129 is a medium-severity command injection vulnerability in BlackBerry GEMS versions 2.1.5.3 to 2.2.22.25, published on 16 Dec 2016. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A remote shell execution vulnerability in the BlackBerry Good Enterprise Mobility Server (GEMS) implementation of the Apache Karaf command shell in GEMS versions 2.1.5.3 to 2.2.22.25 allows remote attackers to obtain local administrator rights on the GEMS server via commands executed on the Karaf command shell.

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

It affects 1 product.


Products: Blackberry Good Enterprise Mobility Server.

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

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

## Is CVE-2016-3129 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-3129 is a medium-severity command injection vulnerability in BlackBerry GEMS versions 2.1.5.3 to 2.2.22.25, published on 16 Dec 2016. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-3129 in the wild and no public exploit code.

Affected product: BlackBerry GEMS versions 2.1.5.3 to 2.2.22.25. 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-3129/ (Markdown: https://insights.sbomify.com/CVE-2016-3129/index.md)
```

## Sources

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

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