# GHSA-p4m5-32pr-2hqr: PyPop C extensions possible vulnerability: missing arguments and redundant null pointers

> Code scanning identified potential issues in PyPop C extensions involving incorrect function calls and redundant null pointers, requiring an upgrade to the latest version.

- **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:** 26 Feb 2024

## What is GHSA-p4m5-32pr-2hqr?

GHSA-p4m5-32pr-2hqr is a vulnerability in pypop-genomics, published on 26 Feb 2024. 

### Official description

### Impact
Code scanning revealed possible vulnerability in C extensions for PyPop: incorrect function calls (missing arguments or wrongly typed arguments) and redundant null pointers.

### Patches
The problem has been patched and fixed in the latest release of PyPop: 1.0.2. Please upgrade your PyPop installation via:

```
pip install -U pypop-genomics
```

### Workarounds
No. Upgrade to the latest package: 1.0.2.

### References
N/A

## Which versions are affected by GHSA-p4m5-32pr-2hqr?

2 open source packages ship an affected version, including pypop-genomics.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pypop-genomics` | PyPI | All versions | 1.0.2 |
| `pypop-genomics` | PyPI | All versions | 1.0.2 |

## How do I fix GHSA-p4m5-32pr-2hqr?

Upgrade pypop-genomics to 1.0.2 or later.

## Is GHSA-p4m5-32pr-2hqr being exploited?

There is no known exploitation of GHSA-p4m5-32pr-2hqr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-p4m5-32pr-2hqr and fix it if it is affected.

What it is: GHSA-p4m5-32pr-2hqr is a vulnerability in pypop-genomics, published on 26 Feb 2024. 
Exploitation: There is no known exploitation of GHSA-p4m5-32pr-2hqr in the wild and no public exploit code.

Affected packages and fixed versions:
- pypop-genomics (PyPI): affected all versions; fixed in 1.0.2
- pypop-genomics (PyPI): affected all versions; fixed in 1.0.2

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/GHSA-p4m5-32pr-2hqr/ (Markdown: https://insights.sbomify.com/GHSA-p4m5-32pr-2hqr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-p4m5-32pr-2hqr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-p4m5-32pr-2hqr/
Summaries are generated and may contain mistakes; the official description above is the record.