cve.bz

CVE-2017-1622 ibm qradar incident forensics: Improper Certificate Validation

7.4 highEPSS 0.6%Fix available

High (7.4) in ibm qradar incident forensics. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
IBM QRadar SIEM 7.2.8 and 7.3 does not validate, or incorrectly validates, a certificate. This weakness might allow an attacker to spoof a trusted entity by using a man-in-the-middle (MITM) attack. IBM X-force ID: 133120.

Severity

CVSS 3.0

7.4 high
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-1622 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-1622?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-1622?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-1622 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ibm:qradar_incident_forensicsfrom 7.2.0 before 7.2.8
ibm:qradar_incident_forensicsfrom 7.3.0 before 7.3.1
ibm:qradar_incident_forensics7.2.8
ibm:qradar_incident_forensics7.2.8:p1
ibm:qradar_incident_forensics7.2.8:p10
ibm:qradar_incident_forensics7.2.8:p11
ibm:qradar_incident_forensics7.2.8:p12
ibm:qradar_incident_forensics7.2.8:p13
ibm:qradar_incident_forensics7.2.8:p3
ibm:qradar_incident_forensics7.2.8:p4
ibm:qradar_incident_forensics7.2.8:p5
ibm:qradar_incident_forensics7.2.8:p6
ibm:qradar_incident_forensics7.2.8:p7
ibm:qradar_incident_forensics7.2.8:p8
ibm:qradar_incident_forensics7.2.8:p9
ibm:qradar_incident_forensics7.3.1
ibm:qradar_incident_forensics7.3.1:p1
ibm:qradar_incident_forensics7.3.1:p2
ibm:qradar_incident_forensics7.3.1:p3
ibm:qradar_incident_forensics7.3.1:p4
ibm:qradar_incident_forensics7.3.1:p5
ibm:qradar_incident_forensics7.3.1:p6

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON