OSV-2025-698 Use-of-uninitialized-value in AesEncrypt_C
Not scored
Published
Check this codebase for OSV-2025-698 and fix it if it is affected.
What it is: OSV-2025-698 is a vulnerability in wolfssl, published on 2 Sep 2025.
Exploitation: There is no known exploitation of OSV-2025-698 in the wild and no public exploit code.
Affected packages and fixed versions:
- wolfssl (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2025-698/ (Markdown: https://insights.sbomify.com/OSV-2025-698/index.md)
Use of uninitialized value in AES encryption function may cause undefined behavior or crashes in cryptographic operations.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2025-698?
OSV-2025-698 is a vulnerability in wolfssl, published on 2 Sep 2025.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=442261624
Crash type: Use-of-uninitialized-value
Crash state:
AesEncrypt_C
wc_AesCbcEncrypt
Encrypt
Which versions are affected by OSV-2025-698?
1 open source package ship an affected version, including wolfssl.
| Package | Affected | Fixed in |
|---|---|---|
wolfssl OSS-Fuzz | All versions | None |
How do I fix OSV-2025-698?
No fix has been published for OSV-2025-698 yet. Limit exposure of the affected software until one is available.
Is OSV-2025-698 being exploited?
There is no known exploitation of OSV-2025-698 in the wild and no public exploit code.