# CVE-2024-50610: Integer overflow in n/a

> An integer signedness error in GSL allows attackers to trigger incorrect memory allocation, potentially leading to denial of service or code execution.

- **Severity:** Low 3.6 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2024
- **Updated:** 30 Oct 2024
- **Also known as:** AZL-51868, AZL-51881, DEBIAN-CVE-2024-50610, GHSA-pj8w-xcg3-82vx, OESA-2024-2361, UBUNTU-CVE-2024-50610, openSUSE-SU-2026:10449-1

## What is CVE-2024-50610?

CVE-2024-50610 is a low-severity vulnerability in n/a, published on 27 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GSL (GNU Scientific Library) through 2.8 has an integer signedness error in gsl_siman_solve_many in siman/siman.c. When params.n_tries is negative, incorrect memory allocation occurs.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gsl` | openSUSE:Tumbleweed | All versions | 2.8-5.1 |

Products: Gnu Gnu Scientific Library.

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

Apply the vendor's patch.

## Is CVE-2024-50610 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50610 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50610 is a low-severity vulnerability in n/a, published on 27 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50610 exists.

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

## Sources

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

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