# CVE-2023-41633: Null dereference in n/a

> A NULL pointer dereference in Catdoc's xls2csv component allows attackers to cause a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Sep 2023
- **Updated:** 1 Oct 2024
- **Also known as:** DEBIAN-CVE-2023-41633, GHSA-pm5p-ff9q-6v54, UBUNTU-CVE-2023-41633

## What is CVE-2023-41633?

CVE-2023-41633 is a medium-severity vulnerability in n/a, published on 1 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Catdoc v0.95 was discovered to contain a NULL pointer dereference via the component xls2csv at src/fileutil.c.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2023-41633?

It affects 1 product.


Products: Fossies Catdoc.

## How do I fix CVE-2023-41633?

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

## Is CVE-2023-41633 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-31979](https://insights.sbomify.com/CVE-2023-31979/): Memory corruption in n/a (high 7.8)
- [CVE-2017-11110](https://insights.sbomify.com/CVE-2017-11110/): Memory corruption in n/a (high 7.8)
- [CVE-2023-46345](https://insights.sbomify.com/CVE-2023-46345/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41633 and fix it if it is affected.

What it is: CVE-2023-41633 is a medium-severity vulnerability in n/a, published on 1 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-41633 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-2023-41633/ (Markdown: https://insights.sbomify.com/CVE-2023-41633/index.md)
```

## Sources

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

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