CVE-2023-49567
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 · uneditedA vulnerability has been identified in the Bitdefender Total Security HTTPS scanning functionality where the product incorrectly checks the site's certificate, which allows an attacker to make MITM SSL connections to an arbitrary site. The product trusts certificates that are issued using the MD5 and SHA1 collision hash functions which allow attackers to create rogue certificates that appear legitimate.
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 confidenceBitdefender Total Security's HTTPS scanning module incorrectly validates SSL/TLS certificates by accepting MD5 and SHA1 hash algorithms, which are vulnerable to collision attacks. This allows an attacker with network positioning to perform MITM attacks by presenting forged certificates that appear legitimate to the scanning engine.
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< 27.0.25.115CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Bitdefender Total Security is installedCheck installed programs in Control Panel > Programs and Features, or run: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Bitdefender*Total Security*'}Affected if Bitdefender Total Security is not present in the installed programs list
-
Check the installed version numberOpen Bitdefender Total Security > Settings > About, or run: (Get-ItemProperty 'HKLM:\Software\Bitdefender' -ErrorAction SilentlyContinue).ProductVersionAffected if The version number is lower than 27.0.25.115 (e.g., 27.0.20.45, 26.0.x.x, etc.)
-
Verify HTTPS scanning module is enabledOpen Bitdefender Total Security > Protection > Web Protection > Settings, and confirm the 'Scan SSL/TLS certificates' or 'HTTPS scanning' option is turned ONAffected if HTTPS scanning is enabled - the vulnerability only applies when this feature is active
You are affected if Bitdefender Total Security version is 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.
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 · scoped27.0.25.115
Organizations should monitor for Bitdefender vendor updates and consider disabling HTTPS scanning as a temporary compensating control until a patch is available, while noting this reduces protection against web-based threats.
Total Security version 27.0.25.115 or later
- Open Bitdefender Total Security application
- Navigate to the Settings or Protection section
- Check for updates or look for the version information
- Update to version 27.0.25.115 or later to address the certificate validation vulnerability
- Restart the system if required after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-49567 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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