{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19240 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19240 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19240 is a medium-severity vulnerability in n/a, published on 22 Nov 2019. 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-19240 and fix it if it is affected.\n\nWhat it is: CVE-2019-19240 is a medium-severity vulnerability in n/a, published on 22 Nov 2019. 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-19240 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-19240/ (Markdown: https://insights.sbomify.com/CVE-2019-19240/index.md)","id":"CVE-2019-19240","markdown":"https://insights.sbomify.com/CVE-2019-19240/index.md","name":"CVE-2019-19240","record":{"aliases":["GHSA-xrwv-jchf-q5j2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GoAhead web server","requires_auth":"none","summary":"An attacker can trigger an uninitialized buffer leak in GoAhead web server by sending a large Host header in a redirected request, potentially exposing sensitive memory data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"goahead","vendor":"embedthis"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"},{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Embedthis GoAhead before 5.0.1 mishandles redirected HTTP requests with a large Host header. The GoAhead WebsRedirect uses a static host buffer that has a limited length and can overflow. This can cause a copy of the Host header to fail, leaving that buffer uninitialized, which may leak uninitialized data in a response.","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":"Information disclosure in n/a","id":"CVE-2019-19240","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-19241"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2019-19235"},"products":["n/a"],"published":"2019-11-22","related":[{"cvss_score":8.1,"headline":"Embedthis GoAhead Remote Code Execution","id":"CVE-2017-17562","kev_date_added":"2021-12-10","published":"2017-12-12"},{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2021-41615","kev_date_added":null,"published":"2022-08-08"},{"cvss_score":9.8,"headline":"Security feature bypass in goahead","id":"CVE-2021-43298","kev_date_added":null,"published":"2022-01-25"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-42342","kev_date_added":null,"published":"2021-10-14"},{"cvss_score":9.8,"headline":"Use after free in EmbedThis","id":"CVE-2019-5096","kev_date_added":null,"published":"2019-12-03"},{"cvss_score":9.8,"headline":"Null dereference in n/a","id":"CVE-2017-1000471","kev_date_added":null,"published":"2018-01-03"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2017-5674","kev_date_added":null,"published":"2017-03-13"}],"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":"An attacker can trigger an uninitialized buffer leak in GoAhead web server by sending a large Host header in a redirected request, potentially exposing sensitive memory data.","url":"https://insights.sbomify.com/CVE-2019-19240/"}