{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-6058 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-6058 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2023-6058 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2023-6058 in the wild and no public exploit code.\n\nAffected product: Bitdefender Total Security. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-6058/ (Markdown: https://insights.sbomify.com/CVE-2023-6058/index.md)","id":"CVE-2023-6058","markdown":"https://insights.sbomify.com/CVE-2023-6058/index.md","name":"CVE-2023-6058","record":{"aliases":["GHSA-h64p-h4x7-h6r6"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Bitdefender Safepay","requires_auth":"none","summary":"Attackers can intercept secure traffic via MITM if users add untrusted sites to exceptions, bypassing certificate validation in Bitdefender Safepay.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Bitdefender","cpe":[{"product":"total_security","vendor":"bitdefender"}],"cvss":{"score":8.6,"severity":"high","source":"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","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"HTTPS Certificate Validation Issue in Bitdefender Safepay (VA-11167)","id":"CVE-2023-6058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2023-6060"},"packages":[],"prev":{"headline":"Insecure Trust of DSA-Signed Certificates in Bitdefender Total Security HTTPS Scanning (VA-11166)","id":"CVE-2023-6057"},"products":["Total Security"],"published":"2024-10-18","related":[{"cvss_score":8.6,"headline":"Insecure Trust of certificates using collision hash functions in Bitdefender Total Security HTTPS Scanning (VA-11239)","id":"CVE-2023-49567","kev_date_added":null,"published":"2024-10-18"},{"cvss_score":8.6,"headline":"Insecure Trust of Basic Constraints certificate in Bitdefender Total Security HTTPS Scanning (VA-11210)","id":"CVE-2023-49570","kev_date_added":null,"published":"2024-10-18"},{"cvss_score":8.6,"headline":"Improper Certificate Validation in Bitdefender Total Security HTTPS Scanning (VA-11158)","id":"CVE-2023-6055","kev_date_added":null,"published":"2024-10-18"},{"cvss_score":8.6,"headline":"Insecure Trust of Self-Signed Certificates in Bitdefender Total Security HTTPS Scanning (VA-11164)","id":"CVE-2023-6056","kev_date_added":null,"published":"2024-10-18"},{"cvss_score":8.6,"headline":"Insecure Trust of DSA-Signed Certificates in Bitdefender Total Security HTTPS Scanning (VA-11166)","id":"CVE-2023-6057","kev_date_added":null,"published":"2024-10-18"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-6183","kev_date_added":null,"published":"2018-03-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-18","vendors":["Bitdefender"]},"summary":"Attackers can intercept secure traffic via MITM if users add untrusted sites to exceptions, bypassing certificate validation in Bitdefender Safepay.","url":"https://insights.sbomify.com/CVE-2023-6058/"}