# CVE-2023-6376: Henschen & Associates court document management software cache uses predictable file names

> Remote attackers can access restricted court documents by predicting cache file names in Henschen & Associates software.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-vqf7-7684-3mjq

## What is CVE-2023-6376?

CVE-2023-6376 is a medium-severity vulnerability in Henschen & Associates court document management software, published on 30 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Henschen & Associates court document management software does not sufficiently randomize file names of cached documents, allowing a remote, unauthenticated attacker to access restricted documents.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Henschen Court Document Management.

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

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

## Is CVE-2023-6376 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6376 is a medium-severity vulnerability in Henschen & Associates court document management software, published on 30 Nov 2023. 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-2023-6376 in the wild and no public exploit code.

Affected product: Henschen & Associates court document management software. 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-6376/ (Markdown: https://insights.sbomify.com/CVE-2023-6376/index.md)
```

## Sources

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

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