# CVE-2024-36735: Other in n/a

> The OneFlow library fails to validate floating-point parameters, potentially leading to undefined behavior or silent errors in deep learning models.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 6 Jun 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-v4wq-4595-gr53

## What is CVE-2024-36735?

CVE-2024-36735 is a medium-severity vulnerability in n/a, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OneFlow-Inc. Oneflow v0.9.1 does not display an error or warning when the oneflow.eye parameter is floating.

Weakness: CWE-704 (Incorrect Type Conversion or Cast)

## Which versions are affected by CVE-2024-36735?

It affects 1 product.


Products: Oneflow Oneflow.

## How do I fix CVE-2024-36735?

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

## Is CVE-2024-36735 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-36736](https://insights.sbomify.com/CVE-2024-36736/): Other in n/a (critical 9.8)
- [CVE-2025-65886](https://insights.sbomify.com/CVE-2025-65886/): Denial of service in n/a (high 7.5)
- [CVE-2025-65888](https://insights.sbomify.com/CVE-2025-65888/): Denial of service in n/a (high 7.5)
- [CVE-2025-65889](https://insights.sbomify.com/CVE-2025-65889/): Denial of service in n/a (high 7.5)
- [CVE-2025-65890](https://insights.sbomify.com/CVE-2025-65890/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36735 and fix it if it is affected.

What it is: CVE-2024-36735 is a medium-severity vulnerability in n/a, published on 6 Jun 2024. 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-2024-36735 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-2024-36735/ (Markdown: https://insights.sbomify.com/CVE-2024-36735/index.md)
```

## Sources

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

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