dbcve.org
Total SecurityApplication · Bitdefender

CVE-2023-6055

HIGH · 7.4 CVSS v3.1 Published 2024-10-18
Fix available
A fix is available. Upgrade to 27.0.25.115 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in Bitdefender Total Security HTTPS scanning functionality where the software fails to properly validate website certificates. Specifically, if a site certificate lacks the "Server Authentication" specification in the Extended Key Usage extension, the product does not verify the certificate's compliance with the site, deeming such certificates as valid. This flaw could allow an attacker to perform a Man-in-the-Middle (MITM) attack, intercepting and potentially altering communications between the user and the website.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Bitdefender Total Security's HTTPS scanning has a certificate validation flaw where it accepts certificates missing the Server Authentication Extended Key Usage (EKU) extension as valid. This allows attackers with network positioning to present invalid certificates and perform MITM attacks, intercepting or modifying HTTPS traffic.

MitigationApply Bitdefender's security update/patch for this vulnerability. Until patched, exercise heightened caution on untrusted networks and monitor for unexpected certificate warnings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Total SecurityApplication
Affected:< 27.0.25.115

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Bitdefender Total Security is installed
    Open Bitdefender Total Security and check the application interface, or look for the installation in Programs and Features (Windows)
    Affected if The product is not installed or a different Bitdefender product is installed (this CVE affects Total Security specifically)
  2. Check the installed version number
    In Bitdefender Total Security, go to Settings > About, or right-click the desktop icon and select 'About'. Compare the version to 27.0.25.115
    Affected if The installed version is lower than 27.0.25.115 (e.g., 27.0.24.x, 27.0.20.x, etc.)
  3. Confirm HTTPS scanning protection is enabled
    In Bitdefender Total Security, go to Protection > Web Protection > Settings and verify that 'Scan SSL' or 'HTTPS scanning' is turned ON
    Affected if HTTPS scanning is enabled - the vulnerability only applies when this feature is active
  4. Verify the Antiphishing and Network Threat Protection modules are active
    In Bitdefender Total Security, go to Protection and ensure Web Protection and Network Threat Protection are enabled
    Affected if The web protection modules are running - the vulnerability is triggered during HTTPS traffic inspection by these modules

You are affected if Bitdefender Total Security is installed with a version below 27.0.25.115 AND HTTPS scanning is enabled in the Web Protection settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 27.0.25.115 or later
Fixed in 27.0.25.115
Interim mitigation

Apply Bitdefender's security update/patch for this vulnerability. Until patched, exercise heightened caution on untrusted networks and monitor for unexpected certificate warnings.

Recommended fix High confidence

27.0.25.115

  1. Open Bitdefender Total Security application
  2. Navigate to the Settings or Updates section
  3. Check the current installed version to confirm it is below 27.0.25.115
  4. Click on Update or Check for Updates to download and install version 27.0.25.115 or later
  5. Restart the computer if prompted after the update completes
  6. Verify the update was successful by checking the installed version number
Caveat Standard update; no major breaking changes expected for typical users

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Total Security Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6055 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6055 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data