# CVE-2023-42183: Security feature bypass in n/a

> Attackers can bypass access restrictions in LOCKSS Daemon by exploiting Unicode normalization flaws, potentially gaining unauthorized access to protected resources.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 15 Dec 2023
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-mgqj-hphf-9588, GHSA-w6m2-rf66-q93w

## What is CVE-2023-42183?

CVE-2023-42183 is a medium-severity vulnerability in n/a, published on 15 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

lockss-daemon (aka Classic LOCKSS Daemon) before 1.77.3 performs post-Unicode normalization, which may allow bypass of intended access restrictions, such as when U+1FEF is converted to a backtick.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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

It affects 1 product.


Products: Lockss Classic Lockss Daemon.

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

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

## Is CVE-2023-42183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42183 is a medium-severity vulnerability in n/a, published on 15 Dec 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-42183 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-42183/ (Markdown: https://insights.sbomify.com/CVE-2023-42183/index.md)
```

## Sources

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

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