CVE-2025-32914

What it actually does

Out-of-bounds read in soup_multipart_new_from_message() triggered by crafted HTTP multipart messages, enabling remote memory disclosure or application crash.

Why it matters to the business

Potential exposure of sensitive process memory or service disruption in JBoss Enterprise Application Platform and dependent systems using the affected HornetQ packages.

How an attack unfolds

Attacker sends a maliciously crafted HTTP request containing malformed multipart data to a server process using vulnerable libsoup code; the soup_multipart_new_from_message function processes the input and reads past allocated buffer boundaries.

How to fix it

Upgrade all listed packages to the exact fixed versions provided: eap7-hornetq, eap7-hornetq-commons, eap7-hornetq-core-client and eap7-hornetq-jms-client at 2.4.11-1.Final_redhat_00001.1.el9eap (EL9), 2.4.11-1.Final_redhat_00001.1.el7eap (EL7) and 2.4.11-1.Final_redhat_00001.1.el8eap (EL8).

How to confirm the fix worked

Confirm installed package versions match the fixed releases above; re-test with boundary-case multipart payloads to verify absence of out-of-bounds behavior.

Typical attack path

1. Craft HTTP request with oversized or malformed multipart boundary data
2. Deliver request to any exposed endpoint processed by libsoup
3. Invoke soup_multipart_new_from_message() during message parsing
4. Trigger out-of-bounds memory read resulting in data leakage or crash

How to detect it

Search application and system logs for repeated crashes or error messages during multipart message handling; monitor for unexpected process terminations in HornetQ components.

What your security team should do

• Apply the listed package updates across all affected JBoss EAP 7.4 deployments
• Prioritize internet-facing instances given the network attack vector
• Review application logs for abnormal multipart parsing failures after patching