dbcve.org
Total SecurityApplication · Bitdefender

CVE-2023-49570

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 trusts a certificate issued by an entity that isn't authorized to issue certificates. This occurs when the "Basic Constraints" extension in the certificate indicates that it is meant to be an "End Entity”. 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

The HTTPS scanning module in Bitdefender Total Security fails to properly validate the Basic Constraints extension in X.509 certificates. When a certificate identifies itself as an 'End Entity' (CA:FALSE) rather than a Certificate Authority, the software incorrectly trusts it for certificate chain validation. This allows an attacker with a specially crafted certificate to impersonate trusted websites and intercept TLS traffic.

MitigationBitdefender must update certificate validation logic to reject certificates where Basic Constraints indicate CA:FALSE when used as intermediate signing certificates. Users should monitor for official vendor patches and ensure HTTPS scanning is disabled until the fix is applied if high-risk.

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. Confirm Bitdefender Total Security installation
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\Bitdefender for the product folder
    Affected if Bitdefender Total Security is present on the system
  2. Identify installed version number
    Right-click the Bitdefender icon in the system tray and select 'About,' or check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Bitdefender\DesktopXML\ProductVersion
    Affected if Version is present and less than 27.0.25.115
  3. Verify HTTPS scanning module is active
    Open Bitdefender main interface, go to Protection > Web Protection, or open Settings > General > Advanced and check if 'Scan SSL' or 'HTTPS scanning' is enabled
    Affected if HTTPS/Traffic scanning is turned on and the version is below 27.0.25.115
  4. Cross-reference version against affected range
    Compare the installed version number to the vulnerable range: any version below 27.0.25.115 is affected
    Affected if Installed version is less than 27.0.25.115 AND HTTPS scanning module is enabled

You are affected if Bitdefender Total Security version is below 27.0.25.115 and the HTTPS scanning or Traffic Scanning feature is currently enabled.

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

Bitdefender must update certificate validation logic to reject certificates where Basic Constraints indicate CA:FALSE when used as intermediate signing certificates. Users should monitor for official vendor patches and ensure HTTPS scanning is disabled until the fix is applied if high-risk.

Recommended fix High confidence

27.0.25.115

  1. Open the Bitdefender Total Security application
  2. Navigate to the 'Settings' or 'Protection' section
  3. Look for 'Update' or 'Software Update' options
  4. Click to check for updates and install the latest version
  5. Alternatively, download the latest version (27.0.25.115 or higher) from the official Bitdefender website: www.bitdefender.com
  6. Restart the computer after the update completes
  7. Verify the installed version is 27.0.25.115 or higher

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

Fix this in Total Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49570 — 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-49570 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