{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-6022 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-6022 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-6022 is a high-severity vulnerability in n/a, published on 27 Feb 2016. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-6022 and fix it if it is affected.\n\nWhat it is: CVE-2015-6022 is a high-severity vulnerability in n/a, published on 27 Feb 2016. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-6022 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-6022/ (Markdown: https://insights.sbomify.com/CVE-2015-6022/index.md)","id":"CVE-2015-6022","markdown":"https://insights.sbomify.com/CVE-2015-6022/index.md","name":"CVE-2015-6022","record":{"aliases":["GHSA-vvg3-32px-m85m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"QNAP Signage Station","requires_auth":"low_privilege","summary":"Remote authenticated users can execute arbitrary code by uploading and accessing an executable file in QNAP Signage Station.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"signage_station","vendor":"qnap"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Unrestricted file upload vulnerability in QNAP Signage Station before 2.0.1 allows remote authenticated users to execute arbitrary code by uploading an executable file, and then accessing this file via an unspecified URL.","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-6022","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2015"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2015-6023"},"packages":[],"prev":{"headline":"Cross-site scripting in Spiceworks Desktop before 2015-12-01","id":"CVE-2015-6021"},"products":["n/a"],"published":"2016-02-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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote authenticated users can execute arbitrary code by uploading and accessing an executable file in QNAP Signage Station.","url":"https://insights.sbomify.com/CVE-2015-6022/"}