Attack Chain

1. Attacker observes a victim authenticating to the /api/xmlrpc/ endpoint, capturing the Unix timestamp of the login event via network timing or exposed logs.
2. The attacker estimates the microsecond portion of the timestamp based on observed network latency or other side-channel information.
3. The attacker reconstructs the MD5 hash format using the known timestamp and the estimated microsecond window.
4. The attacker bounds the LCG float component based on server PID ranges (if known or leaked via /server-status).
5. The attacker generates a candidate pool of MD5 hashes based on the reconstructed format and LCG variations.
6. The attacker sends a series of crafted HTTP POST requests to the /api/xmlrpc/ endpoint, each containing a different candidate session ID within the <methodCall><params><param><value><string>{CANDIDATE_SESSION_ID}</string></value></param></params></methodCall> XML structure.
7. The attacker monitors the HTTP responses for a non-fault response (HTTP 200 containing data), indicating a successful session hijack.
8. Upon successful hijack, the attacker uses the valid session ID to access privileged API endpoints, such as those for managing product catalogs, customer data, or orders, to perform malicious actions such as data exfiltration, order fraud, or inventory manipulation.

Impact

Successful exploitation of this vulnerability allows an attacker to hijack active API sessions, granting them full control over the compromised account. This can lead to data exfiltration of customer PII, order history, and payment methods. Attackers can also manipulate orders by creating, canceling, or changing shipping addresses. Further, they can modify prices, inject malicious products, or zero out stock, leading to significant financial and operational damage. This vulnerability affects all legacy API protocols, including XML-RPC, SOAP v1, SOAP v2, and REST APIs.

Recommendation

• Apply the vendor-supplied patch to replace the time-derived token with a cryptographically secure random value, as described in the advisory by updating app/code/core/Mage/Api/Model/Session.php file.
• Implement rate limiting on API endpoints like /api/xmlrpc/ to prevent high-speed online brute-force attacks.
• Monitor web server logs for unusual POST requests to the /api/xmlrpc/, /api/soap/, /api/v2_soap/, and /api/rest/ endpoints using the Sigma rule provided to detect potential session hijacking attempts.