{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-3150 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-3150 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-3150 is a critical path traversal vulnerability in n/a, published on 27 Aug 2010. 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-2010-3150 and fix it if it is affected.\n\nWhat it is: CVE-2010-3150 is a critical path traversal vulnerability in n/a, published on 27 Aug 2010. 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-2010-3150 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-2010-3150/ (Markdown: https://insights.sbomify.com/CVE-2010-3150/index.md)","id":"CVE-2010-3150","markdown":"https://insights.sbomify.com/CVE-2010-3150/index.md","name":"CVE-2010-3150","record":{"aliases":["GHSA-9j9q-pp23-rfvx"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Adobe Premiere Pro","requires_auth":"none","summary":"Local attackers can execute arbitrary code via DLL hijacking when users open malicious project files in Adobe Premiere Pro.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"premier_pro_cs4","vendor":"adobe"}],"cvss":{"score":9.3,"severity":"critical","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Untrusted search path vulnerability in Adobe Premier Pro CS4 4.0.0 (314 (MC: 160820)) allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse ibfs32.dll that is located in the same folder as a .pproj, .prfpset, .prexport, .prm, .prmp, .prpreset, .prproj, .prsl, .prtl, or .vpr file.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2010-08-25","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2010-08-25","kind":"exploitdb","ref":"14771","stars":null,"title":"Adobe Premier Pro CS4 - 'ibfs32.dll' DLL Hijacking"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2010-3150","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2010"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2010-3151"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2010-3149"},"products":["n/a"],"published":"2010-08-27","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary code via DLL hijacking when users open malicious project files in Adobe Premiere Pro.","url":"https://insights.sbomify.com/CVE-2010-3150/"}