CVE-2021-27756
CVE-2021-27756 is a high-severity vulnerability in Hcltech Bigfix Compliance with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.
Key facts
- Severity: High (CVSS 3.x base score 7.5)
- CVSS v2: 4.3
- EPSS exploit prediction: 1% (42nd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-327
- Affected product: Hcltech Bigfix Compliance
- Published:
- Last modified:
Description
"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."
Frequently asked questions
- What is 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."
- How severe is CVE-2021-27756?
- CVE-2021-27756 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
- Is CVE-2021-27756 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (42nd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2021-27756?
- CVE-2021-27756 affects Hcltech Bigfix Compliance. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2021-27756?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2021-27756 published?
- CVE-2021-27756 was published on 2022-03-04 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:hcltech:bigfix_compliance:*:*:*:*:*:*:*:*
More vulnerabilities in Hcltech Bigfix Compliance
- CVE-2024-30125 — Medium (CVSS 6.2): HCL BigFix Compliance server can respond with an HTTP status of 500, indicating a server-side error that may cause the…
- CVE-2024-42212 — Medium (CVSS 5.4): HCL BigFix Compliance is affected by an improper or missing SameSite attribute. This can lead to Cross-Site Request…
- CVE-2024-30140 — Medium (CVSS 5.4): HCL BigFix Compliance is affected by unvalidated redirects and forwards. The HOST header can be manipulated by an…
- CVE-2023-37525 — Medium (CVSS 5.3): A sensitive information disclosure in HCL BigFix Compliance allows a remote attacker to access files under the WEB-INF…
- CVE-2024-42213 — Medium (CVSS 5.3): HCL BigFix Compliance is affected by inclusion of temporary files left in the production environment. An attacker…
- CVE-2024-30141 — Medium (CVSS 4.7): HCL BigFix Compliance is vulnerable to the generation of error messages containing sensitive information. Detailed…
All CVEs affecting Hcltech Bigfix Compliance →
Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities
- CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
- CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
- CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
- CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
- CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…
- CVE-2025-13476 — Critical (CVSS 9.8): Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS…
Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →