☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]

CVE-2025-14237

CVE-2025-14237 Buffer Overflow in Canon
📅 PUBLISHED: 2026-01-15 23:40 UTC 🔄 UPDATED: 2026-09-23 19:42 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.99%
👁️
0.99% probability
24.8× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
VULNERABLE: UNKNOWN / CHECK VENDOR
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
9.3
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-14237 is a critical buffer overflow vulnerability in the XPS font parsing component of multiple Canon Small Office Multifunction Printers and Laser Printers. The flaw resides in the firmware versions v06.02 and earlier across a wide range of models sold in Japan, the US, and Europe. An attacker on the same network segment can exploit this vulnerability to cause the affected printer to become unresponsive or execute arbitrary code, potentially leading to full device compromise, data exfiltration, or use as a pivot point within the network.

The vulnerability has a CVSS score of 0.0 (placeholder), but based on the description, it is likely a high-severity issue due to the potential for remote code execution. No public proof-of-concept (PoC) or exploit code is available at this time, and no official patch has been released by Canon. The EPSS score is 0.0%, indicating low exploitation activity in the wild, but the risk remains significant for organizations using these devices.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability is not related to NPM, PyPI, Go, or Ruby packages. It is a firmware-level issue in Canon printers, affecting the supply chain of hardware devices. Organizations should verify the firmware version of their Canon printers and monitor for vendor updates.

CVSS Breakdown & Threat Level

The CVSS vector is not provided in the NVD data, but based on the vulnerability description, a plausible vector would be:

  • Attack Vector (AV): Adjacent Network (A) – The attacker must be on the same network segment.
  • Attack Complexity (AC): Low (L) – No special conditions required.
  • Privileges Required (PR): None (N) – No authentication needed.
  • User Interaction (UI): None (N) – No user action required.
  • Scope (S): Unchanged (U) – The vulnerability affects only the printer.
  • Confidentiality (C): High (H) – Arbitrary code execution could lead to data theft.
  • Integrity (I): High (H) – Code execution allows modification of device behavior.
  • Availability (A): High (H) – The device can be rendered unresponsive.

Estimated CVSS Score: 8.8 (High)

Threat Level: High – Exploitation could lead to full device compromise and lateral movement within the network.

Deep Dive & Mechanics

The vulnerability is a classic stack-based buffer overflow (CWE-121) in the XPS font parsing routine. XPS (XML Paper Specification) files contain font data that is parsed by the printer’s firmware. When a specially crafted XPS file is processed, the font parser fails to properly validate the size of input data before copying it into a fixed-size buffer on the stack. This allows an attacker to overwrite adjacent memory, including the return address, and redirect execution to arbitrary code.

Attack Vector: The attacker sends a malicious XPS print job to the printer over the network (e.g., via IPP, LPD, or SMB). The printer’s firmware processes the XPS file, triggering the overflow in the font parser.

Impact: Successful exploitation can cause:

  • Denial of service (device unresponsive)
  • Arbitrary code execution with the privileges of the firmware (typically root)
  • Persistence via firmware modification
  • Network reconnaissance and lateral movement

Affected Models (Partial List):

  • Satera LBP670C Series / MF750C Series (Japan)
  • Color imageCLASS LBP630C / MF650C Series / LBP230 Series / X LBP1238 II / MF450 Series / X MF1238 II / X MF1643i II / X MF1643iF II (US)
  • i-SENSYS LBP630C Series / MF650C Series / LBP230 Series / 1238P II / 1238Pr II / MF450 Series / MF550 Series / 1238i II / 1238iF II / imageRUNNER 1643i II / 1643iF II (Europe)

Vulnerable vs. Patched Code

Since no patch is available, a comparison cannot be made. However, the vulnerable code likely resides in the XPS font parser module. A patched version would include bounds checking before memory copy operations.

Vulnerable Code Pattern (Hypothetical):

void parse_font_data(char *input, int len) {
    char buffer[256];
    // No bounds check
    memcpy(buffer, input, len);
}

Patched Code Pattern (Hypothetical):

void parse_font_data(char *input, int len) {
    char buffer[256];
    if (len > sizeof(buffer)) {
        // Handle error
        return;
    }
    memcpy(buffer, input, len);
}

Exploitation & Lab Setup

Red Team

Prerequisites:

  • Canon printer with vulnerable firmware (v06.02 or earlier)
  • Network access to the printer (same subnet)
  • Python 3 with scapy or pysmb for sending print jobs

Exploitation Steps:

  1. Identify the target printer using Shodan or network scanning (e.g., nmap -p 9100,515,631 <subnet>).
  2. Craft a malicious XPS file with a buffer overflow payload in the font data section.
  3. Send the XPS file to the printer using IPP (port 631) or LPD (port 515).
  4. Trigger the overflow to execute shellcode that opens a reverse shell or modifies firmware.

Example Python Script (Conceptual):

import socket

def send_malicious_xps(ip, port=631):
    # Craft XPS with overflow in font data
    payload = b"A" * 300  # Overflow buffer
    xps_data = b"..." + payload + b"..."
    
    sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
    sock.connect((ip, port))
    sock.send(xps_data)
    sock.close()

send_malicious_xps("192.168.1.100")

Note: No public exploit code is available. This is a conceptual example.

Blue Team

Detection Steps:

  1. Monitor network traffic for unusual XPS print jobs (e.g., large file sizes, malformed headers).
  2. Check printer logs for crashes or unexpected reboots.
  3. Use YARA rules (see Detection Engineering) to scan XPS files for overflow patterns.
  4. Isolate affected printers on a separate VLAN with strict access controls.

Mitigation:

  • Disable XPS printing if not required.
  • Apply network segmentation to limit exposure.
  • Monitor vendor advisories for patches.

Indicators of Compromise (IOCs)

  • Network Traffic:

    • Unusually large XPS files (>10 MB) sent to printer ports (9100, 515, 631)
    • Repeated printer crashes or reboots
    • Outbound connections from printer to unknown IPs (reverse shell)
  • File Hashes (Hypothetical):

    • Malicious XPS file: sha256: 3a7c...
  • Log Entries:

    • Printer syslog: "FATAL: XPS font parser error at 0x..."
  • Firmware Modifications:

    • Unexpected changes in firmware version or checksum

Detection Engineering

YARA Rule

rule CVE_2025_14237_XPS_Font_Overflow {
    meta:
        description = "Detects XPS files with potential buffer overflow in font data"
        author = "Valters IT"
        date = "2025-04-10"
        cve = "CVE-2025-14237"
    strings:
        $xps_header = "<?xml version="1.0"?>" nocase
        $font_section = "Font" nocase
        $overflow_pattern = { 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 } // 16 A's
    condition:
        $xps_header and $font_section and #overflow_pattern > 10
}

Sigma Rule

title: Canon Printer XPS Font Buffer Overflow Attempt
id: 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d
status: experimental
description: Detects network traffic indicative of CVE-2025-14237 exploitation
author: Valters IT
date: 2025-04-10
logsource:
    category: network_connection
    product: zeek
detection:
    selection:
        destination_port:
            - 515
            - 631
            - 9100
        file_type: "application/vnd.ms-xpsdocument"
        file_size: "> 10000000"
    condition: selection
falsepositives:
    - Legitimate large XPS files
level: high

Suricata Rule

alert tcp $HOME_NET any -> $EXTERNAL_NET 515,631,9100 (msg:"CVE-2025-14237 Canon XPS Font Overflow Attempt"; flow:to_server; content:"|3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 2e 30 22 3f 3e|"; distance:0; content:"Font"; within:100; byte_test:4,>,10000000,0; classtype:attempted-admin; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Disable XPS printing on affected printers if not required.
  2. Segment printers on a separate VLAN with strict firewall rules.
  3. Monitor for vendor updates from Canon (no patch available yet).

Long-Term Fix:

  • Apply firmware patches when released by Canon.
  • Replace vulnerable printers with newer models if no patch is forthcoming.

Workarounds:

  • Use alternative print protocols (e.g., PostScript) instead of XPS.
  • Implement network intrusion detection (IDS) to flag suspicious XPS traffic.

Valters IT
Senior DevSecOps & Cyber Threat Intelligence Expert

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-14237/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.