# CVE-2023-6341: Catalis CM360 allows authentication bypass

> Remote attackers can bypass authentication to view sensitive court documents by manipulating URL identifiers in Catalis CMS360.

- **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-v85w-cvcx-r2qh

## What is CVE-2023-6341?

CVE-2023-6341 is a medium-severity authentication bypass vulnerability in Catalis CMS360, published on 30 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Catalis (previously Icon Software) CMS360 allows a remote, unauthenticated attacker to view sensitive court documents by modifying document and other identifiers in URLs. The impact varies based on the intention and configuration of a specific CMS360 installation.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Catalisgov Cms360.

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

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

## Is CVE-2023-6341 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6341 is a medium-severity authentication bypass vulnerability in Catalis CMS360, 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-6341 in the wild and no public exploit code.

Affected product: Catalis CMS360. 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-6341/ (Markdown: https://insights.sbomify.com/CVE-2023-6341/index.md)
```

## Sources

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

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