{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41526 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41526 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41526 is a high-severity memory corruption vulnerability in n/a, published on 6 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-41526 and fix it if it is affected.\n\nWhat it is: CVE-2022-41526 is a high-severity memory corruption vulnerability in n/a, published on 6 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-41526 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-41526/ (Markdown: https://insights.sbomify.com/CVE-2022-41526/index.md)","id":"CVE-2022-41526","markdown":"https://insights.sbomify.com/CVE-2022-41526/index.md","name":"CVE-2022-41526","record":{"aliases":["GHSA-hg64-cj58-6ffc"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TOTOLINK router","requires_auth":"low_privilege","summary":"An authenticated attacker can trigger a stack overflow in the diagnosis configuration function, potentially leading to arbitrary code execution on the router.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nr1800x_firmware","vendor":"totolink"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"TOTOLINK NR1800X V9.1.0u.6279_B20210910 was discovered to contain an authenticated stack overflow via the ip parameter in the setDiagnosisCfg function.","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":"Memory corruption in n/a","id":"CVE-2022-41526","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-41527"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2022-41525"},"products":["n/a"],"published":"2022-10-06","related":[{"cvss_score":9.8,"headline":"Totolink NR1800X cstecgi.cgi loginAuth stack-based overflow","id":"CVE-2023-7220","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-36340","kev_date_added":null,"published":"2023-10-16"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-41518","kev_date_added":null,"published":"2022-10-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-41522","kev_date_added":null,"published":"2022-10-06"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-41525","kev_date_added":null,"published":"2022-10-06"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2025-45842","kev_date_added":null,"published":"2025-05-08"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2025-45843","kev_date_added":null,"published":"2025-05-08"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"An authenticated attacker can trigger a stack overflow in the diagnosis configuration function, potentially leading to arbitrary code execution on the router.","url":"https://insights.sbomify.com/CVE-2022-41526/"}