Listen to this Post
CVE-2025-36134 exploits a vulnerability in IBM Sterling B2B Integrator and Sterling File Gateway where a sensitive cookie does not have the SameSite attribute set securely. The SameSite attribute is crucial for protecting cookies from being sent in cross-site requests, which can prevent attacks like CSRF and XSS. In this case, the absence or improper configuration of this attribute allows attackers to potentially intercept or steal the cookie during cross-site interactions. This cookie likely contains session tokens or authentication details, and its compromise could lead to unauthorized access to sensitive data. The vulnerability affects versions 6.0.0.0 through 6.1.2.7, 6.2.0.0 through 6.2.0.5, and 6.2.1.1. When a user accesses the application, the cookie is set without the SameSite restriction, making it vulnerable to being included in requests from third-party websites. Attackers can craft malicious web pages that trigger requests to the vulnerable application, capturing the cookie if the user is logged in. This can result in session hijacking, where the attacker impersonates the user and gains access to sensitive information. The issue stems from improper cookie handling in the application code, specifically in how cookies are configured for security. By exploiting this, attackers can bypass same-origin policies and extract sensitive information from the cookie. This type of vulnerability is particularly dangerous in multi-domain deployments or when users visit untrusted sites. The disclosure of sensitive information can include personal data, financial information, or other confidential details managed by the B2B integrator. To mitigate, the SameSite attribute should be set to ‘Strict’ or ‘Lax’ to restrict cookie sending to same-site requests only.
Platform: IBM Sterling Systems
Version: 6.0.0.0-6.2.1.1
Vulnerability: Insecure SameSite cookie
Severity: Medium
date: 11/25/2025
Prediction: Patch expected Q1 2026
What Undercode Say:
Check cookie headers for SameSite attribute
curl -I https://target.com | grep -i set-cookie
Example vulnerable response
Set-Cookie: sessionid=abc; HttpOnly
Secure example with SameSite
Set-Cookie: sessionid=abc; HttpOnly; SameSite=Strict
How Exploit:
Attacker creates malicious site embedding requests to vulnerable application. User visits site while authenticated, cookie sent cross-site. Attacker captures cookie via network sniffing or JavaScript. Session hijacking enables unauthorized access.
Protection from this CVE:
Set SameSite=Strict for cookies. Update to patched versions. Implement secure cookie policies. Use HTTPS exclusively.
Impact:
Sensitive information disclosure. Session hijacking risks. Unauthorized data access. Potential compliance violations.
🎯Let’s Practice Exploiting & Learn Patching For Free:
Sources:
Reported By: nvd.nist.gov
Extra Source Hub:
Undercode
