# CVE-2023-30259: Information disclosure in n/a

> Attackers can obtain sensitive information via a crafted DBF file in LibreCAD's importshp plugin.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** Yes
- **Published:** 28 Jun 2023
- **Updated:** 27 Nov 2024
- **Also known as:** DEBIAN-CVE-2023-30259, GHSA-6hr9-9v75-c7qh, UBUNTU-CVE-2023-30259

## What is CVE-2023-30259?

CVE-2023-30259 is a medium-severity vulnerability in n/a, published on 28 Jun 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

A Buffer Overflow vulnerability in importshp plugin in LibreCAD 2.2.0 allows attackers to obtain sensitive information via a crafted DBF file.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Librecad Librecad.

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

Upgrade to a fixed version.

## Is CVE-2023-30259 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19105](https://insights.sbomify.com/CVE-2018-19105/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-30259 is a medium-severity vulnerability in n/a, published on 28 Jun 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30259 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-2023-30259/ (Markdown: https://insights.sbomify.com/CVE-2023-30259/index.md)
```

## Sources

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

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