# CVE-2024-32151: Information disclosure in Multiple MFPs (multifunction printers)

> Attackers can retrieve decrypted user passwords from coredump files on affected multifunction printers, exposing sensitive credentials.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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:** 26 Nov 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-27gg-q2pj-f574

## What is CVE-2024-32151?

CVE-2024-32151 is a medium-severity vulnerability in Sharp Corporation Multiple MFPs (multifunction printers), published on 26 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

User passwords are decrypted and stored on memory before any user logged in. Those decrypted passwords can be retrieved from the coredump file. As for the details of affected product names, model numbers, and versions, refer to the information provided by the respective vendors listed under [References].

Weakness: CWE-257 (Storing Passwords in a Recoverable Format)

## Which versions are affected by CVE-2024-32151?


## How do I fix CVE-2024-32151?

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

## Is CVE-2024-32151 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32151 and fix it if it is affected.

What it is: CVE-2024-32151 is a medium-severity vulnerability in Sharp Corporation Multiple MFPs (multifunction printers), published on 26 Nov 2024. 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-2024-32151 in the wild and no public exploit code.

Affected product: Sharp Corporation Multiple MFPs (multifunction printers). 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-2024-32151/ (Markdown: https://insights.sbomify.com/CVE-2024-32151/index.md)
```

## Sources

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

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