{"answers":{"affected":"It affects 20 products.","exploited":"There is no known exploitation of CVE-2024-41338 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-41338 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41338 is a high-severity vulnerability in Draytek Vigor3910 Firmware, published on 27 Feb 2025. 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-41338 and fix it if it is affected.\n\nWhat it is: CVE-2024-41338 is a high-severity vulnerability in Draytek Vigor3910 Firmware, published on 27 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-41338 in the wild and no public exploit code.\n\nAffected product: Draytek Vigor3910 Firmware. 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-41338/ (Markdown: https://insights.sbomify.com/CVE-2024-41338/index.md)","id":"CVE-2024-41338","markdown":"https://insights.sbomify.com/CVE-2024-41338/index.md","name":"CVE-2024-41338","record":{"aliases":["GHSA-22qr-hr3v-pmr2"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Draytek router firmware","requires_auth":"none","summary":"Attackers can cause a Denial of Service on Draytek routers via a crafted DHCP request due to a NULL pointer dereference.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vigor165_firmware","vendor":"draytek"},{"product":"vigor166_firmware","vendor":"draytek"},{"product":"vigor2133_firmware","vendor":"draytek"},{"product":"vigor2135_firmware","vendor":"draytek"},{"product":"vigor2620_firmware","vendor":"draytek"},{"product":"vigor2762_firmware","vendor":"draytek"},{"product":"vigor2765_firmware","vendor":"draytek"},{"product":"vigor2766_firmware","vendor":"draytek"},{"product":"vigor2832_firmware","vendor":"draytek"},{"product":"vigor2860_firmware","vendor":"draytek"},{"product":"vigor2862_firmware","vendor":"draytek"},{"product":"vigor2865_firmware","vendor":"draytek"},{"product":"vigor2866_firmware","vendor":"draytek"},{"product":"vigor2925_firmware","vendor":"draytek"},{"product":"vigor2926_firmware","vendor":"draytek"},{"product":"vigor2927_firmware","vendor":"draytek"},{"product":"vigor2962_firmware","vendor":"draytek"},{"product":"vigor3910_firmware","vendor":"draytek"},{"product":"vigor3912_firmware","vendor":"draytek"},{"product":"vigorlte200_firmware","vendor":"draytek"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"A NULL pointer dereference in Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862/2926 prior to v3.9.9.4, Vigor 2133/2762/2832 prior to v3.9.8, Vigor 2135/2765/2766 prior to v4.4.5.1, Vigor 2865/2866/2927 prior to v4.4.5.3, Vigor 2962/3910 prior to v4.3.2.7, Vigor 3912 prior to v4.3.5.2, and Vigor 2925 up to v3.9.6 allows attackers to cause a Denial of Service (DoS) via a crafted DHCP request.","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":"Null dereference in n/a","id":"CVE-2024-41338","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"draytek:vigor3910_firmware","products":["draytek:vigor3910_firmware"],"type":"null_dereference","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2024-41339"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2024-41336"},"products":["n/a"],"published":"2025-02-27","related":[{"cvss_score":8.8,"headline":"Security feature bypass in n/a","id":"CVE-2024-41334","kev_date_added":null,"published":"2025-02-27"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2024-41339","kev_date_added":null,"published":"2025-02-27"},{"cvss_score":8.4,"headline":"File upload in n/a","id":"CVE-2024-41340","kev_date_added":null,"published":"2025-02-27"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can cause a Denial of Service on Draytek routers via a crafted DHCP request due to a NULL pointer dereference.","url":"https://insights.sbomify.com/CVE-2024-41338/"}