# CVE-2018-14439: Business logic in n/a

> Attackers can exploit floating-point handling errors in the EOS SDK to trigger unintended currency transfers, affecting blockchain transaction integrity.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 20 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5gqv-phj4-9rwg

## What is CVE-2018-14439?

CVE-2018-14439 is a high-severity vulnerability in n/a, published on 20 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

espritblock eos4j, an unofficial SDK for EOS, through 2018-07-12 mishandles floating-point numbers with more than four digits after the decimal point, which might allow attackers to trigger currency transfers of unintended amounts.

Weakness: CWE-682 (Incorrect Calculation)

## Which versions are affected by CVE-2018-14439?

It affects 1 product.


Products: Eblock Eos4j.

## How do I fix CVE-2018-14439?

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

## Is CVE-2018-14439 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14439 and fix it if it is affected.

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

## Sources

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

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