# CVE-2019-7727: Misconfiguration in n/a

> Remote attackers can execute arbitrary code because the default configuration exposes an unauthenticated JMX/RMI interface on all network interfaces.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w3m3-6r64-x8g3

## What is CVE-2019-7727?

CVE-2019-7727 is a critical vulnerability in n/a, published on 23 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In NICE Engage through 6.5, the default configuration binds an unauthenticated JMX/RMI interface to all network interfaces, without restricting registration of MBeans, which allows remote attackers to execute arbitrary code via the RMI protocol by using the JMX connector. The observed affected TCP port is 6338 but, based on the product's configuration, a different one could be vulnerable.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2019-7727?

It affects 1 product.


Products: Nice Engage.

## How do I fix CVE-2019-7727?

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

## Is CVE-2019-7727 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7727 and fix it if it is affected.

What it is: CVE-2019-7727 is a critical vulnerability in n/a, published on 23 Apr 2019. 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-2019-7727 in the wild and no public exploit code.

Affected product: n/a. 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-2019-7727/ (Markdown: https://insights.sbomify.com/CVE-2019-7727/index.md)
```

## Sources

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

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