{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3369 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-3369 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3369 is a high-severity vulnerability in Bitdefender Engines, published on 1 Nov 2022. 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-2022-3369 and fix it if it is affected.\n\nWhat it is: CVE-2022-3369 is a high-severity vulnerability in Bitdefender Engines, published on 1 Nov 2022. 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-2022-3369 in the wild and no public exploit code.\n\nAffected product: Bitdefender Engines. 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-2022-3369/ (Markdown: https://insights.sbomify.com/CVE-2022-3369/index.md)","id":"CVE-2022-3369","markdown":"https://insights.sbomify.com/CVE-2022-3369/index.md","name":"CVE-2022-3369","record":{"aliases":["GHSA-mjr5-h3w4-973v"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bitdefender Antivirus","requires_auth":"none","summary":"Attackers can delete privileged registry keys via symlink abuse in Bitdefender Engines, enabling privilege escalation.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Bitdefender","cpe":[{"product":"engines","vendor":"bitdefender"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"An Improper Access Control vulnerability in the bdservicehost.exe component, as used in Bitdefender Engines for Windows, allows an attacker to delete privileged registry keys by pointing a Registry symlink to a privileged key. This issue affects: Bitdefender Engines versions prior to 7.92659. It also affects Bitdefender Antivirus Free, Bitdefender Antivirus Plus, Bitdefender Internet Security, Bitdefender Total Security, as well as Bitdefender Endpoint Security Tools for Windows with engine versions prior to 7.92659.","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":"Improper handling of registry symbolic links in Bitdefender Engines","id":"CVE-2022-3369","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in Chrome","id":"CVE-2022-3370"},"packages":[],"prev":{"headline":"Software Updater of Avira Security for Windows vulnerable to Privilege Escalation","id":"CVE-2022-3368"},"products":["Engines"],"published":"2022-11-01","related":[{"cvss_score":9,"headline":"Incomplete validation in detection code in Bitdefender Engines (VA-8589)","id":"CVE-2020-8100","kev_date_added":null,"published":"2020-05-15"},{"cvss_score":8.1,"headline":"Out of Bounds Memory Corruption Issue in CEVA Engine","id":"CVE-2023-3633","kev_date_added":null,"published":"2023-07-14"},{"cvss_score":5.9,"headline":"Bitdefender ceva_emu.cvd module denial-of-service (VA-8766)","id":"CVE-2020-8110","kev_date_added":null,"published":"2020-10-02"},{"cvss_score":5.9,"headline":"Bitdefender ace.xmd parser out-of-bounds write (VA-8772)","id":"CVE-2020-8109","kev_date_added":null,"published":"2020-10-01"},{"cvss_score":3.2,"headline":"Local Privilege Escalation in Bitdefender Engines (VA-8953)","id":"CVE-2020-15731","kev_date_added":null,"published":"2020-09-30"}],"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":"2025-05-02","vendors":["Bitdefender"]},"summary":"Attackers can delete privileged registry keys via symlink abuse in Bitdefender Engines, enabling privilege escalation.","url":"https://insights.sbomify.com/CVE-2022-3369/"}