Bigfix compliance
This hub aggregates every CVE we track for Bigfix compliance, a product in the enterprise software space. Use it to gauge the current risk picture and drill into individual advisories.
14
CVEs tracked
0
Critical
1
High
0
In CISA KEV
Severity distribution
MEDIUM10LOW3HIGH1
Monthly trend
0
3
0
0
0
0
0
2
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
2024-102026-09
Latest CVEs
The 14 most recently published vulnerabilities affecting Bigfix compliance.
- CVE-2023-37525HCL BigFix Compliance is vulnerable to a sensitive information disclosure5.3
- CVE-2024-42213HCL BigFix Compliance is affected by inclusion of temporary files left in the production environment5.3
- CVE-2024-42212HCL BigFix Compliance is affected by an improper or missing SameSite attribute5.4
- CVE-2024-30142HCL BigFix Compliance is affected by a missing secure flag on a cookie3.8
- CVE-2024-30141HCL BigFix Compliance is vulnerable to the generation of error messages containing sensitive information4.7
- CVE-2024-30140HCL BigFix Compliance is affected by unvalidated redirects and forwards5.4
- CVE-2024-30126HCL BigFix Compliance is affected by a missing X-Frame-Options Header vulnerability4.7
- CVE-2024-30125HCL BigFix Compliance is affected by an internal server error6.2
- CVE-2024-23551HCL BigFix Compliance is potentially affected by Oracle database credentials stored at endpoint6.5
- CVE-2021-27756"TLS-RSA cipher suites are not disabled in BigFix Compliance up to v2.0.5. If TLS 2.0 and secure ciphers are not enabled then an attacker can passively record traffic and later decrypt it."7.5
- CVE-2017-1200IBM 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 m...3.7
- CVE-2017-1177IBM BigFix Compliance 1.7 through 1.9.91 discloses sensitive information to unauthorized users. The information can be used to mount further attacks on the system. IBM X-Force ID: 123429.5.3
- CVE-2017-1202IBM BigFix Compliance 1.7 through 1.9.91 (TEMA SUAv1 SCA SCM) is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim...5.4
- CVE-2017-1198IBM BigFix Compliance 1.7 through 1.9.91 (TEMA SUAv1 SCA SCM) stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs...3.7
Product normalization is registry-driven with AI assist and human review. How it works