CVE-2023-42522

7.5 HIGH

📋 TL;DR

This vulnerability allows remote attackers to crash the scanning engine in multiple WithSecure security products by sending a specially crafted PE file containing a malformed import struct. Affected users include organizations running WithSecure endpoint protection, server security, and Linux security products across Windows, Mac, and Linux platforms.

💻 Affected Systems

Products:
  • WithSecure Client Security
  • WithSecure Server Security
  • WithSecure Email and Server Security
  • WithSecure Elements Endpoint Protection
  • WithSecure Client Security for Mac
  • WithSecure Elements Endpoint Protection for Mac
  • Linux Security 64
  • Linux Protection
  • WithSecure Atlant
Versions: Client Security 15, Server Security 15, Email and Server Security 15, Elements Endpoint Protection 17+, Client Security for Mac 15, Elements Endpoint Protection for Mac 17+, Linux Security 64 12.0, Linux Protection 12.0, Atlant 1.0.35-1
Operating Systems: Windows, macOS, Linux
Default Config Vulnerable: ⚠️ Yes
Notes: All affected products with scanning engines enabled are vulnerable in default configurations.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Denial of service causing scanning engine crash, potentially disabling real-time protection and leaving systems vulnerable to other attacks during the outage.

🟠

Likely Case

Temporary disruption of scanning services requiring service restart, with possible missed detections during downtime.

🟢

If Mitigated

Minimal impact with proper network segmentation and monitoring to detect and respond to scanning engine crashes.

🌐 Internet-Facing: MEDIUM - Attackers could exploit this by sending malicious files to internet-facing services using these products, but requires specific targeting.
🏢 Internal Only: MEDIUM - Internal attackers or malware could trigger the crash to disable protection mechanisms.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires sending a specially crafted PE file to trigger the parsing vulnerability, which is relatively straightforward for attackers with knowledge of PE file structures.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific patched versions

Vendor Advisory: https://www.withsecure.com/en/support/security-advisories

Restart Required: Yes

Instructions:

1. Check vendor advisory for specific patched versions. 2. Update all affected WithSecure products to latest versions. 3. Restart scanning services after update. 4. Verify update completion through management console.

🔧 Temporary Workarounds

Temporary scanning bypass

all

Configure scanning exclusions for PE files from untrusted sources (not recommended long-term)

🧯 If You Can't Patch

  • Implement network segmentation to limit exposure of scanning services
  • Monitor for scanning engine crashes and implement automated restart procedures

🔍 How to Verify

Check if Vulnerable:

Check product version against affected versions list in vendor advisory

Check Version:

Check through WithSecure management console or product about dialog

Verify Fix Applied:

Verify product version is updated beyond affected versions and scanning engine is running normally

📡 Detection & Monitoring

Log Indicators:

  • Scanning engine crash logs
  • Unexpected service restarts
  • Failed scan attempts

Network Indicators:

  • Unusual PE file transfers to systems with scanning services

SIEM Query:

Search for 'scanning engine crash', 'service restart', or 'protection disabled' events in WithSecure logs

🔗 References

📤 Share & Export