Ironport Email Security ApplianceApplication · Cisco

CVE-2023-31488

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Hyland Perceptive Filters releases before 2023-12-08 (e.g., 11.4.0.2647), as used in Cisco IronPort Email Security Appliance Software, Cisco Secure Email Gateway, and various non-Cisco products, allow attackers to trigger a segmentation fault and execute arbitrary code via a crafted document.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Hyland Perceptive Filters contains a memory corruption vulnerability (likely buffer overflow) in document parsing that allows attackers to trigger a segmentation fault and achieve arbitrary code execution via crafted malicious documents. The CVSS 9.8 indicates network-exploitable, low-complexity attacks without authentication.

MitigationUpgrade Hyland Perceptive Filters to versions released on or after 2023-12-08. For Cisco products, apply corresponding security updates for IronPort Email Security Appliance Software and Cisco Secure Email Gateway.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ironport Email Security ApplianceApplication
Affected:all versions
Secure Email Gateway FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco IronPort Email Security Appliance in your environment
    Locate and confirm any Cisco IronPort Email Security Appliance devices deployed on your network by checking your asset inventory or network documentation
    Affected if The device is present and running any version of IronPort Email Security Appliance firmware
  2. Identify Cisco Secure Email Gateway in your environment
    Locate and confirm any Cisco Secure Email Gateway devices deployed on your network by checking your asset inventory or network documentation
    Affected if The device is present and running any version of Cisco Secure Email Gateway firmware
  3. Verify if document filtering or content scanning is enabled
    Access the appliance administrative interface or command-line interface and check whether document parsing, content filtering, or attachment scanning features are enabled. Look for settings related to Perceptive Filters, content filters, or document inspection
    Affected if Document parsing and content scanning features are actively enabled on the appliance, as the vulnerability triggers during malicious document processing
  4. Check for Hyland Perceptive Filters integration
    Examine the appliance configuration for any reference to Hyland Perceptive Filters, document filters, or third-party content filtering modules. This may appear in the邮件安全策略, content filter rules, or scanning profiles
    Affected if Hyland Perceptive Filters or associated document parsing components are configured or integrated with the email security appliance

Your environment is affected if you run any version of Cisco IronPort Email Security Appliance or Cisco Secure Email Gateway with document parsing or content filtering features enabled that utilize Hyland Perceptive Filters for processing incoming documents.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Hyland Perceptive Filters to versions released on or after 2023-12-08. For Cisco products, apply corresponding security updates for IronPort Email Security Appliance Software and Cisco Secure Email Gateway.

Fix this in Ironport Email Security Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31488 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31488 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data