# CVE-2025-45331: Null dereference in n/a

> A null pointer dereference in brplot's data processing module causes segmentation faults and program crashes, leading to denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-hw53-4q7v-6mcg

## What is CVE-2025-45331?

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

### Official description

brplot v420.69.1 contains a Null Pointer Dereference (NPD) vulnerability in the br_dagens_handle_once function of its data processing module, leading to unpredictable program behavior, causing segmentation faults, and program crashes.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-45331?

It affects 1 product.


Products: Ricko Brplot.

## How do I fix CVE-2025-45331?

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

## Is CVE-2025-45331 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-45331 and fix it if it is affected.

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

## Sources

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

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