{"answers":{"affected":"It affects 21 products.","exploited":"There is no known exploitation of CVE-2024-45263 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45263 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45263 is a high-severity vulnerability in n/a, published on 24 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45263 and fix it if it is affected.\n\nWhat it is: CVE-2024-45263 is a high-severity vulnerability in n/a, published on 24 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-45263 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-2024-45263/ (Markdown: https://insights.sbomify.com/CVE-2024-45263/index.md)","id":"CVE-2024-45263","markdown":"https://insights.sbomify.com/CVE-2024-45263/index.md","name":"CVE-2024-45263","record":{"aliases":["GHSA-vpfw-56r4-6hcq"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GL-iNet router","requires_auth":"none","summary":"Attackers can upload arbitrary files to GL-iNet routers, leading to information leakage and complete device control.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"a1300_firmware","vendor":"gl-inet"},{"product":"ar300m16_firmware","vendor":"gl-inet"},{"product":"ar300m_firmware","vendor":"gl-inet"},{"product":"ar750_firmware","vendor":"gl-inet"},{"product":"ar750s_firmware","vendor":"gl-inet"},{"product":"ax1800_firmware","vendor":"gl-inet"},{"product":"axt1800_firmware","vendor":"gl-inet"},{"product":"b1300_firmware","vendor":"gl-inet"},{"product":"b3000_firmware","vendor":"gl-inet"},{"product":"e750_firmware","vendor":"gl-inet"},{"product":"mt1300_firmware","vendor":"gl-inet"},{"product":"mt2500_firmware","vendor":"gl-inet"},{"product":"mt3000_firmware","vendor":"gl-inet"},{"product":"mt300n-v2_firmware","vendor":"gl-inet"},{"product":"mt6000_firmware","vendor":"gl-inet"},{"product":"sft1200_firmware","vendor":"gl-inet"},{"product":"x3000_firmware","vendor":"gl-inet"},{"product":"x300b_firmware","vendor":"gl-inet"},{"product":"x750_firmware","vendor":"gl-inet"},{"product":"xe3000_firmware","vendor":"gl-inet"},{"product":"xe300_firmware","vendor":"gl-inet"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/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 issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2. The upload interface allows the uploading of arbitrary files to the device. Once the device executes the files, it can lead to information leakage, enabling complete control.","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-2024-45263","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2024-45264"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2024-45262"},"products":["n/a"],"published":"2024-10-24","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2024-39225","kev_date_added":null,"published":"2024-08-06"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2024-39227","kev_date_added":null,"published":"2024-08-06"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2024-39228","kev_date_added":null,"published":"2024-08-06"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2024-45262","kev_date_added":null,"published":"2024-10-24"},{"cvss_score":8,"headline":"Missing authorization in n/a","id":"CVE-2024-45260","kev_date_added":null,"published":"2024-10-24"},{"cvss_score":8,"headline":"Auth bypass in n/a","id":"CVE-2024-45261","kev_date_added":null,"published":"2024-10-24"}],"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":"2024-10-28","vendors":["n/a"]},"summary":"Attackers can upload arbitrary files to GL-iNet routers, leading to information leakage and complete device control.","url":"https://insights.sbomify.com/CVE-2024-45263/"}