# CVE-2023-6058: HTTPS Certificate Validation Issue in Bitdefender Safepay (VA-11167)

> Attackers can intercept secure traffic via MITM if users add untrusted sites to exceptions, bypassing certificate validation in Bitdefender Safepay.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2024
- **Updated:** 18 Oct 2024
- **Also known as:** GHSA-h64p-h4x7-h6r6

## What is CVE-2023-6058?

CVE-2023-6058 is a high-severity vulnerability in Bitdefender Total Security, published on 18 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in Bitdefender Safepay's handling of HTTPS connections. The issue arises when the product blocks a connection due to an untrusted server certificate but allows the user to add the site to exceptions, resulting in the product trusting the certificate for subsequent HTTPS scans. This vulnerability allows an attacker to perform a Man-in-the-Middle (MITM) attack by using a self-signed certificate, which the product will trust after the site has been added to exceptions. This can lead to the interception and potential alteration of secure communications.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2023-6058?

It affects 1 product.


Products: Bitdefender Total Security.

## How do I fix CVE-2023-6058?

No fix has been published for CVE-2023-6058 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-6058 being exploited?

There is no known exploitation of CVE-2023-6058 in the wild and no public exploit code.

## Other vulnerabilities in Bitdefender Total Security

- [CVE-2023-49567](https://insights.sbomify.com/CVE-2023-49567/): Insecure Trust of certificates using collision hash functions in Bitdefender Total Security HTTPS Scanning (VA-11239) (high 8.6)
- [CVE-2023-49570](https://insights.sbomify.com/CVE-2023-49570/): Insecure Trust of Basic Constraints certificate in Bitdefender Total Security HTTPS Scanning (VA-11210) (high 8.6)
- [CVE-2023-6055](https://insights.sbomify.com/CVE-2023-6055/): Improper Certificate Validation in Bitdefender Total Security HTTPS Scanning (VA-11158) (high 8.6)
- [CVE-2023-6056](https://insights.sbomify.com/CVE-2023-6056/): Insecure Trust of Self-Signed Certificates in Bitdefender Total Security HTTPS Scanning (VA-11164) (high 8.6)
- [CVE-2023-6057](https://insights.sbomify.com/CVE-2023-6057/): Insecure Trust of DSA-Signed Certificates in Bitdefender Total Security HTTPS Scanning (VA-11166) (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6058 and fix it if it is affected.

What it is: CVE-2023-6058 is a high-severity vulnerability in Bitdefender Total Security, published on 18 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-6058 in the wild and no public exploit code.

Affected product: Bitdefender Total Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-6058/ (Markdown: https://insights.sbomify.com/CVE-2023-6058/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6058
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6058
- OSV: https://osv.dev/vulnerability/CVE-2023-6058

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6058/
Summaries are generated and may contain mistakes; the official description above is the record.