# HSEC-2024-0006: fromIntegral: conversion error

> Incorrect integer conversions in Haskell's fromIntegral function can cause data corruption or crashes, potentially leading to buffer overflows.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Nov 2025

## What is HSEC-2024-0006?

HSEC-2024-0006 is a vulnerability in base, published on 14 Nov 2025. 

### Official description

# `fromIntegral`: conversion error

`fromIntegral` may result in coercion errors when used with optimization flags `-O1` or `-O2`
in the following situation:

- Converting negative `Int` to `Natural` does not throw an arithmetic underflow error
- Converting large `Integer` greater than 2^64 to `Natural` overflow.

For the most part, these errors in and of themselves result only in availability and data integrity issues.
However, in some circumstances, they may result in other, more complicated security related flaws, such as buffer overflow conditions.

## Which versions are affected by HSEC-2024-0006?

1 open source package ship an affected version, including base.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `base` | Hackage | From 4.15.0.0 | 4.15.1.0 |

## How do I fix HSEC-2024-0006?

Upgrade base to 4.15.1.0 or later.

## Is HSEC-2024-0006 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for HSEC-2024-0006 and fix it if it is affected.

What it is: HSEC-2024-0006 is a vulnerability in base, published on 14 Nov 2025. 
Exploitation: There is no known exploitation of HSEC-2024-0006 in the wild and no public exploit code.

Affected packages and fixed versions:
- base (Hackage): affected from 4.15.0.0; fixed in 4.15.1.0

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/HSEC-2024-0006/ (Markdown: https://insights.sbomify.com/HSEC-2024-0006/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/HSEC-2024-0006

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