{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-19840 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19840 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19840 is a critical memory corruption vulnerability in n/a, published on 22 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19840 and fix it if it is affected.\n\nWhat it is: CVE-2019-19840 is a critical memory corruption vulnerability in n/a, published on 22 Jan 2020. 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-2019-19840 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-2019-19840/ (Markdown: https://insights.sbomify.com/CVE-2019-19840/index.md)","id":"CVE-2019-19840","markdown":"https://insights.sbomify.com/CVE-2019-19840/index.md","name":"CVE-2019-19840","record":{"aliases":["GHSA-2xqq-rhmm-h69h"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruckus Unleashed","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on Ruckus Unleashed devices via a stack-based buffer overflow in the zap component.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"unleashed","vendor":"ruckuswireless"},{"product":"zonedirector_1200_firmware","vendor":"ruckuswireless"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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-787","name":"Out-of-bounds Write"}],"description":"A stack-based buffer overflow in zap_parse_args in zap.c in zap in Ruckus Unleashed through 200.7.10.102.64 allows remote code execution via an unauthenticated HTTP 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":"Memory corruption in n/a","id":"CVE-2019-19840","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2019-19841"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-19839"},"products":["n/a"],"published":"2020-01-22","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-19838","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-19839","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2019-19836","kev_date_added":null,"published":"2020-01-22"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-19841","kev_date_added":null,"published":"2020-01-22"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-19842","kev_date_added":null,"published":"2020-01-22"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2019-19843","kev_date_added":null,"published":"2020-01-22"}],"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-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code on Ruckus Unleashed devices via a stack-based buffer overflow in the zap component.","url":"https://insights.sbomify.com/CVE-2019-19840/"}