# CVE-2019-0729: Weak cryptography in Java SDK for Azure IoT

> Attackers can predict symmetric keys due to weak randomness in Azure IoT Java SDK, leading to privilege escalation.

- **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:** 6 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-62f9-2v42-4h92

## What is CVE-2019-0729?

CVE-2019-0729 is a critical vulnerability in Microsoft Java SDK for Azure IoT, published on 6 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Elevation of Privilege vulnerability exists in the way Azure IoT Java SDK generates symmetric keys for encryption, allowing an attacker to predict the randomness of the key, aka 'Azure IoT Java SDK Elevation of Privilege Vulnerability'.

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

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

It affects 1 product.


Products: Microsoft Java Software Development Kit.

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

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

## Is CVE-2019-0729 being exploited?

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

## Other vulnerabilities in Microsoft Java SDK for Azure IoT

- [CVE-2019-0741](https://insights.sbomify.com/CVE-2019-0741/): Information disclosure in Java SDK for Azure IoT (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0729 is a critical vulnerability in Microsoft Java SDK for Azure IoT, published on 6 Mar 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-0729 in the wild and no public exploit code.

Affected product: Microsoft Java SDK for Azure IoT. 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-0729/ (Markdown: https://insights.sbomify.com/CVE-2019-0729/index.md)
```

## Sources

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

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