{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-6057 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-6057 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-6057 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-6057 and fix it if it is affected.\n\nWhat it is: CVE-2023-6057 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-6057 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-6057/ (Markdown: https://insights.sbomify.com/CVE-2023-6057/index.md)","id":"CVE-2023-6057","markdown":"https://insights.sbomify.com/CVE-2023-6057/index.md","name":"CVE-2023-6057","record":{"aliases":["GHSA-hm9p-89r4-c9g7"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bitdefender Total Security","requires_auth":"none","summary":"Attackers can bypass HTTPS scanning and perform man-in-the-middle attacks on arbitrary sites using DSA-signed certificates due to improper certificate chain validation.","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 discovered in Bitdefender Total Security HTTPS scanning functionality that results in the improper trust of certificates issued using the DSA signature algorithm. The product does not properly check the certificate chain, allowing an attacker to establish MITM SSL connections to arbitrary sites using a DSA-signed certificate.","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":"Insecure Trust of DSA-Signed Certificates in Bitdefender Total Security HTTPS Scanning (VA-11166)","id":"CVE-2023-6057","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":"HTTPS Certificate Validation Issue in Bitdefender Safepay (VA-11167)","id":"CVE-2023-6058"},"packages":[],"prev":{"headline":"Insecure Trust of Self-Signed Certificates in Bitdefender Total Security HTTPS Scanning (VA-11164)","id":"CVE-2023-6056"},"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":"HTTPS Certificate Validation Issue in Bitdefender Safepay (VA-11167)","id":"CVE-2023-6058","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-11-21","vendors":["Bitdefender"]},"summary":"Attackers can bypass HTTPS scanning and perform man-in-the-middle attacks on arbitrary sites using DSA-signed certificates due to improper certificate chain validation.","url":"https://insights.sbomify.com/CVE-2023-6057/"}