{"answers":{"affected":"2 open source packages ship an affected version, including @janhq/core. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36858 exists.","fix":"No fix has been published for CVE-2024-36858 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-36858 is a critical vulnerability in n/a, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-36858 and fix it if it is affected.\n\nWhat it is: CVE-2024-36858 is a critical vulnerability in n/a, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36858 exists.\n\nAffected packages and fixed versions:\n- @janhq/core (npm): affected all versions up to 0.1.11; no fix listed\n- @janhq/core (npm): affected all versions up to 0.1.11; no fix listed\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-2024-36858/ (Markdown: https://insights.sbomify.com/CVE-2024-36858/index.md)","id":"CVE-2024-36858","markdown":"https://insights.sbomify.com/CVE-2024-36858/index.md","name":"CVE-2024-36858","record":{"aliases":["GHSA-qfjh-mvq6-c5p8"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jan AI desktop app","requires_auth":"none","summary":"Attackers can execute arbitrary code by uploading crafted files via the writeFileSync interface in the Jan desktop application.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jan","vendor":"homebrew"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"An arbitrary file upload vulnerability in the /v1/app/writeFileSync interface of Jan v0.4.12 allows attackers to execute arbitrary code via uploading a crafted file.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-36858.yaml","stars":null,"title":"Jan v0.4.12 - Arbitrary File Upload"}],"tier":"weaponised"},"has_fix":false,"headline":"Jan path traversal vulnerability","id":"CVE-2024-36858","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-36877"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.11"],"package":"@janhq/core","purl":null,"source":"GHSA-qfjh-mvq6-c5p8"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.11"],"package":"@janhq/core","purl":"pkg:npm/%40janhq/core","source":"GHSA-qfjh-mvq6-c5p8"}],"prev":{"headline":"Jan path traversal vulnerability","id":"CVE-2024-36857"},"products":["n/a"],"published":"2024-06-04","related":[{"cvss_score":9.8,"headline":"Jan path traversal vulnerability","id":"CVE-2024-37273","kev_date_added":null,"published":"2024-06-04"},{"cvss_score":7.5,"headline":"Jan path traversal vulnerability","id":"CVE-2024-36857","kev_date_added":null,"published":"2024-06-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by uploading crafted files via the writeFileSync interface in the Jan desktop application.","url":"https://insights.sbomify.com/CVE-2024-36858/"}