# CVE-2019-11219: Weak cryptography in n/a

> Predictable device IDs in Shenzhen Yunni Technology iLnkP2P allow remote attackers to bypass security controls and connect to arbitrary devices.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-54gm-47p9-xr3r

## What is CVE-2019-11219?

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

### Official description

The algorithm used to generate device IDs (UIDs) for devices that utilize Shenzhen Yunni Technology iLnkP2P suffers from a predictability flaw that allows remote attackers to establish direct connections to arbitrary devices.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Ilnkp2p Project Ilnkp2p.

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

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

## Is CVE-2019-11219 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-11220](https://insights.sbomify.com/CVE-2019-11220/): Information disclosure in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11219 is a high-severity vulnerability in n/a, published on 26 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-11219 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-11219/ (Markdown: https://insights.sbomify.com/CVE-2019-11219/index.md)
```

## Sources

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

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