# CVE-2017-3225: Weak cryptography in U-Boot

> U-Boot's AES-CBC implementation uses a zero initialization vector, allowing attackers to decrypt environment data if encryption is enabled.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-3225, GHSA-x8ww-88gq-789c

## What is CVE-2017-3225?

CVE-2017-3225 is a medium-severity vulnerability in Das U-Boot, published on 24 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Das U-Boot is a device bootloader that can read its configuration from an AES encrypted file. For devices utilizing this environment encryption mode, U-Boot's use of a zero initialization vector may allow attacks against the underlying cryptographic implementation and allow an attacker to decrypt the data. Das U-Boot's AES-CBC encryption feature uses a zero (0) initialization vector. This allows an attacker to perform dictionary attacks on encrypted data produced by Das U-Boot to learn information about the encrypted data.

Weakness: CWE-310, CWE-329 (Generation of Predictable IV with CBC Mode)

## Which versions are affected by CVE-2017-3225?

It affects 1 product.


Products: Denx U-Boot.

## How do I fix CVE-2017-3225?

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

## Is CVE-2017-3225 being exploited?

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

## Other vulnerabilities in Das U-Boot

- [CVE-2022-34835](https://insights.sbomify.com/CVE-2022-34835/): Integer overflow in n/a (critical 9.8)
- [CVE-2022-30767](https://insights.sbomify.com/CVE-2022-30767/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-8432](https://insights.sbomify.com/CVE-2020-8432/): Use after free in n/a (critical 9.8)
- [CVE-2019-14192](https://insights.sbomify.com/CVE-2019-14192/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-14193](https://insights.sbomify.com/CVE-2019-14193/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3225 and fix it if it is affected.

What it is: CVE-2017-3225 is a medium-severity vulnerability in Das U-Boot, published on 24 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3225 in the wild and no public exploit code.

Affected product: Das U-Boot. 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-2017-3225/ (Markdown: https://insights.sbomify.com/CVE-2017-3225/index.md)
```

## Sources

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

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