{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41418 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41418 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41418 is a high-severity vulnerability in n/a, published on 19 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-41418 and fix it if it is affected.\n\nWhat it is: CVE-2022-41418 is a high-severity vulnerability in n/a, published on 19 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-41418 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-2022-41418/ (Markdown: https://insights.sbomify.com/CVE-2022-41418/index.md)","id":"CVE-2022-41418","markdown":"https://insights.sbomify.com/CVE-2022-41418/index.md","name":"CVE-2022-41418","record":{"aliases":["GHSA-mfh9-9gwj-9822"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"BlogEngine.NET","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code by uploading a crafted PNG file to the BlogEngine.NET application.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"blogengine.net","vendor":"blogengine"}],"cvss":{"score":7.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An issue in the component BlogEngine/BlogEngine.NET/AppCode/Api/UploadController.cs of BlogEngine.NET v3.3.8.0 allows attackers to execute arbitrary code via uploading a crafted PNG file.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2022-41418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-41419"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-41417"},"products":["n/a"],"published":"2022-12-19","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-33404","kev_date_added":null,"published":"2023-06-26"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2022-41417","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2018-14485","kev_date_added":null,"published":"2019-05-07"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2019-6714","kev_date_added":null,"published":"2019-03-17"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2022-25591","kev_date_added":null,"published":"2022-05-13"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2019-10720","kev_date_added":null,"published":"2019-06-21"},{"cvss_score":8.5,"headline":"Stored cross-site scripting in BlogEngine.NET version 3.3.8.0","id":"CVE-2023-22856","kev_date_added":null,"published":"2023-03-06"}],"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-04-17","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by uploading a crafted PNG file to the BlogEngine.NET application.","url":"https://insights.sbomify.com/CVE-2022-41418/"}