{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-3380 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-3380 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-3380 is a medium-severity vulnerability in n/a, published on 29 Oct 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2005-3380 and fix it if it is affected.\n\nWhat it is: CVE-2005-3380 is a medium-severity vulnerability in n/a, published on 29 Oct 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2005-3380 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2005-3380/ (Markdown: https://insights.sbomify.com/CVE-2005-3380/index.md)","id":"CVE-2005-3380","markdown":"https://insights.sbomify.com/CVE-2005-3380/index.md","name":"CVE-2005-3380","record":{"aliases":["GHSA-cfgm-r5hj-fcvm"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Panda Titanium Antivirus","requires_auth":"none","summary":"Remote attackers can bypass virus scanning in Panda Titanium by crafting files with misleading magic bytes, allowing malicious code execution on the end system.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"titanium_2005","vendor":"panda"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"Multiple interpretation error in Panda Titanium 2005 4.02.01 allows remote attackers to bypass virus scanning via a file such as BAT, HTML, and EML with an \"MZ\" magic byte sequence which is normally associated with EXE, which causes the file to be treated as a safe type that could still be executed as a dangerous file type by applications on the end system, as demonstrated by a \"triple headed\" program that contains EXE, EML, and HTML content, aka the \"magic byte bug.\"","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":"Security feature bypass in n/a","id":"CVE-2005-3380","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2005"},"n_packages":0,"n_references":5,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2005-3381"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2005-3379"},"products":["n/a"],"published":"2005-10-29","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can bypass virus scanning in Panda Titanium by crafting files with misleading magic bytes, allowing malicious code execution on the end system.","url":"https://insights.sbomify.com/CVE-2005-3380/"}