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

> Attackers can enumerate valid user accounts on Kyocera TASKalfa printers by observing distinct error messages during login attempts.

- **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:** 3 Nov 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-m7v7-jj45-j87q

## What is CVE-2023-34261?

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

### Official description

Kyocera TASKalfa 4053ci printers through 2VG_S000.002.561 allow identification of valid user accounts via username enumeration because they lead to a "nicht einloggen" error rather than a falsch error.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Kyocera D-Copia253mf Plus Firmware.

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

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

## Is CVE-2023-34261 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-34260](https://insights.sbomify.com/CVE-2023-34260/): Path traversal in n/a (high 7.5)
- [CVE-2020-23575](https://insights.sbomify.com/CVE-2020-23575/): Path traversal in n/a (high 7.5)
- [CVE-2023-34259](https://insights.sbomify.com/CVE-2023-34259/): Path traversal in n/a (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34261 is a medium-severity vulnerability in n/a, published on 3 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34261 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-34261/ (Markdown: https://insights.sbomify.com/CVE-2023-34261/index.md)
```

## Sources

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

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