CVE-2025-22868

What it actually does

The vulnerability allows a malformed token to trigger excessive memory allocation during the parsing process, leading to resource exhaustion.

Why it matters to the business

Systems relying on the affected component may experience denial of service, resulting in operational disruptions and potential loss of availability for connected devices.

How an attack unfolds

An attacker crafts and sends a specially malformed token to the parsing function, causing it to consume unexpected amounts of memory until the system is overwhelmed.

How to fix it

Update to the fixed version in commit 8224b3c49f8bd285ad5658c1b3cd9683d6627bdb for openthread.

How to confirm the fix worked

Verify the software version matches the fixed commit and test with malformed inputs to ensure no excessive memory use.

Typical attack path

1. Identify a service or device using the vulnerable parsing logic
2. Craft a malicious malformed token
3. Transmit the token to trigger parsing
4. Observe resource consumption leading to denial of service

How to detect it

Monitor logs for parsing errors or spikes in memory usage during token processing.

What your security team should do

• Apply the available fix promptly
• Monitor for unusual memory patterns in parsing components
• Implement input validation where possible