Improper certificate validation in IBM BigFix Compliance
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-295.
Summary
IBM BigFix Compliance 1.7 through 1.9.91 (TEMA SUAv1 SCA SCM) 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. The software might connect to a malicious host while believing it is a trusted host, or the software might be deceived into accepting spoofed data that appears to originate from a trusted host. IBM X-Force ID: 123675.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2017-1200
- 2026-10-03 Alias added: GHSA-67jr-4gph-p24h
- 2026-10-21 EPSS moved to the 50th–90th percentile
References
More IBM Bigfix Compliance vulnerabilities
- TI-2017-00960 Information disclosure in IBM BigFix Compliance CVSS 3.0MEDIUM 5.3
- TI-2017-00980 Injection in IBM BigFix Compliance CVSS 3.0MEDIUM 5.4
- TI-2017-00976 Sensitive information in log files in IBM BigFix Compliance CVSS 3.0MEDIUM 5.3
Sources
- CVE-2017-1200 · CVE Program
- CVE-2017-1200 · NVD
- FIRST EPSS
- GHSA-67jr-4gph-p24h · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences