IBM QRadar EDR Multiple Vulnerabilities Advisory (XSS/Weak Crypto/Session Mgmt)

Thinking Process: 1. Analyze the Request: Role: Professional translator specializing in cybersecurity. Task: Translate a Chinese vulnerability intelligence summary to English. Constraint 1: Maintain all Markdown formatting intact. Constraint 2: Do not add any introductory or concluding remarks. Constraint 3: Just output the English translation. 2. Analyze the Source Text: Title: (Key Vulnerability Information Summary) Section 1: (Vulnerability Overview) Content: IBM Security QRadar EDR Software has multiple vulnerabilities, potentially leading to XSS attacks or decrypting sensitive info via weak crypto. Fixed in version 3.12.24. Section 2: (Vulnerability Details) Item 1: Description: DOMPurify details, bypass via nested tech, Prototype Pollution, XSS. Fixed in DOMPurify 2.5.4 and 3.1.3. CWE: CWE-1333: Inefficient Regular Expression Complexity (Wait, the Chinese says "不高效的正则表达式复杂性" which maps to CWE-1333, but the description talks about DOMPurify/XSS bypass. This looks like a potential mismatch in the source text itself, but as a translator, I should translate what is written, not correct the technical accuracy unless it's obviously a typo I can infer. However, CWE-1333 is indeed "Inefficient Regular Expression Complexity". The description mentions DOMPurify bypass. I will translate faithfully.) CVSS: 6.1 Item 2: Description: IBM Security ReaQta encryption strength lower than expected, attacker might decrypt sensitive info. CWE: CWE-326: Inadequate Encryption Strength CVSS: 5.9 Item 3: Description: IBM Security ReaQta session not invalidated after expiry, impersonation possible. CWE: CWE-613: Insufficient Session Expiration CVSS: 6.3 Item 4: Description: Similar to CVE-2025-36377, same description and impact. CWE: CWE-613: Insufficient Session Expiration CVSS: 6.3 Section 3: (Affected Products and Versions) Product: IBM Security QRadar EDR Version Range: 3.12 - 3.12.23 Section 4: (Remediation Measures) Content: IBM recommends updating to 3.12.24. Supports auto and manual approval policies for upgrade. 3. Drafting the Translation (Iterative Process): Title: -> Overview: -> -> Details: -> CVE 1: -> -> -> CVE 2: -> -> -> CVE 3: -> -> -> CVE 4: -> -> -> Affected: -> -> -> Remediation: -> -> 4. Review and Refine: Check Markdown syntax (headers, bolding, lists). Ensure terminology is accurate for cybersecurity context (e.g., "Prototype Pollution", "XSS", "CVSS Score", "CWE"). Check for flow and readability. Self-Correction on CVE-1 Description: "XSS 指定规范库" -> "XSS specification library" or "XSS sanitization library"? DOMPurify is often called a "sanitizer". The Chinese says "指定规范库" (specification library). I will stick close to the text but "sanitization" might be more accurate technically. However, as a translator, I should translate the meaning. "Specification library" sounds a bit odd for DOMPurify. Let's look at the Chinese: "XSS 指定规范库". It likely means a library that enforces XSS specifications. "XSS sanitization library" is the common term. But "specification library" is literal. Given the instruction is to translate, I should aim for accuracy. "DOMPurify is a DOM-only, ultra-fast, ultra-forgiving XSS specification library..." sounds a bit clunky. Maybe "XSS filtering library"? Let's check common translations for DOMPurify descriptions. Usually "XSS sanitizer". But the text says "规范" (specification/standard). I will use "XSS sanitization library" as it's the standard term for DOMPurify in English security contexts, but "specification" is the literal translation. Let's go with "XSS sanitization library" for professional accuracy, or stick to literal? "Specification library" might confuse readers. Actually, "specification" here might refer to the spec it adheres to. Let's use "XSS sanitization library" as it conveys the function better in English cybersecurity context. Wait, looking closely: "XSS 指定规范库". "指定" could mean "designated" or "specific". "规范" means standard/spec. "Library". I will translate as "XSS sanitization library" because that is what DOMPurify is known as, ensuring the translation is professional. Actually, to be safe and faithful, "XSS specification library" is risky. Let's look at the context: "DOMPurify is a DOM-only...". I will use "XSS sanitization library" as it is the correct technical term. Re-evaluating CVE-1 CWE: The text says CWE-1333 (Inefficient Regular Expression Complexity). The description talks about DOMPurify bypass/Prototype Pollution. This is a known discrepancy in some vulnerability databases (sometimes metadata is wrong). I must translate the text provided, not correct the metadata. So I will translate CWE-1333 as "Inefficient Regular Expression Complexity". Re-evaluating CVE-1 Description: "超快速、超容错" -> "ultra-fast, ultra-forgiving". "深度检查" -> "deep inspection" or "deep scanning". "深度检查" usually implies deep validation. "Deep inspection" works. Re-evaluating CVE-4: "与 CVE-2025-36377 类似，描述及影响相同。" -> "Similar to CVE-2025-36377, with the same description and impact." Remedia

Goal Reached Thanks to every supporter — we hit 100%!

IBM QRadar EDR Multiple Vulnerabilities Advisory (XSS/Weak Crypto/Session Mgmt)