{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-2962 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-2962 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-2962 is a high-severity vulnerability in n/a, published on 13 Jun 2015. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-2962 and fix it if it is affected.\n\nWhat it is: CVE-2015-2962 is a high-severity vulnerability in n/a, published on 13 Jun 2015. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-2962 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-2015-2962/ (Markdown: https://insights.sbomify.com/CVE-2015-2962/index.md)","id":"CVE-2015-2962","markdown":"https://insights.sbomify.com/CVE-2015-2962/index.md","name":"CVE-2015-2962","record":{"aliases":["GHSA-73gj-jrhp-99x5"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"CGI RESCUE BloBee","requires_auth":"unknown","summary":"Remote attackers can write arbitrary files to execute code in CGI RESCUE BloBee, posing a critical risk to web server integrity.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"blobee","vendor":"cgi_rescue"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"CGI RESCUE BloBee 1.20 and earlier allows remote attackers to write to arbitrary files, and consequently execute arbitrary code, via unspecified vectors.","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":"File upload in n/a","id":"CVE-2015-2962","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2015"},"n_packages":0,"n_references":3,"next":{"headline":"paperclip Cross-site Scripting vulnerability","id":"CVE-2015-2963"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2015-2961"},"products":["n/a"],"published":"2015-06-13","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can write arbitrary files to execute code in CGI RESCUE BloBee, posing a critical risk to web server integrity.","url":"https://insights.sbomify.com/CVE-2015-2962/"}