# CVE-2025-48499: Memory corruption in Apoes 2150 N

> A specially crafted IPP or LPD packet can cause a denial-of-service condition on FUJIFILM MFPs, requiring a device reset to recover.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2025
- **Updated:** 7 Aug 2025
- **Also known as:** GHSA-rp36-j278-p677

## What is CVE-2025-48499?

CVE-2025-48499 is a medium-severity memory corruption vulnerability in FUJIFILM Business Innovation Corp. Apoes 2150 N, published on 4 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Out-of-bounds write vulnerability exists in FUJIFILM Business Innovation MFPs. A specially crafted IPP (Internet Printing Protocol) or LPD (Line Printer Daemon) packet may cause a denial-of-service (DoS) condition on an affected MFP. Resetting the MFP is required to recover from the denial-of-service (DoS) condition.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-48499?


## How do I fix CVE-2025-48499?

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

## Is CVE-2025-48499 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48499 and fix it if it is affected.

What it is: CVE-2025-48499 is a medium-severity memory corruption vulnerability in FUJIFILM Business Innovation Corp. Apoes 2150 N, published on 4 Aug 2025. 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-2025-48499 in the wild and no public exploit code.

Affected product: FUJIFILM Business Innovation Corp. Apoes 2150 N. 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-2025-48499/ (Markdown: https://insights.sbomify.com/CVE-2025-48499/index.md)
```

## Sources

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

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