{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13120 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-13120 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-13120 is a high-severity vulnerability in n/a, published on 7 Oct 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-13120 and fix it if it is affected.\n\nWhat it is: CVE-2019-13120 is a high-severity vulnerability in n/a, published on 7 Oct 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-13120 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-13120/ (Markdown: https://insights.sbomify.com/CVE-2019-13120/index.md)","id":"CVE-2019-13120","markdown":"https://insights.sbomify.com/CVE-2019-13120/index.md","name":"CVE-2019-13120","record":{"aliases":["GHSA-vvg7-3vpg-wq97"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Amazon FreeRTOS","requires_auth":"none","summary":"An attacker with MQTT publish authorization can trigger memory leakage in Amazon FreeRTOS by sending malformed packets, exposing arbitrary memory contents.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"amazon_web_services_freertos","vendor":"amazon"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Amazon FreeRTOS up to and including v1.4.8 lacks length checking in prvProcessReceivedPublish, resulting in untargetable leakage of arbitrary memory contents on a device to an attacker. If an attacker has the authorization to send a malformed MQTT publish packet to an Amazon IoT Thing, which interacts with an associated vulnerable MQTT message in the application, specific circumstances could trigger this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2019-13120","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2019-13121"},"packages":[],"prev":{"headline":"libxslt Type Confusion vulnerability that affects Nokogiri","id":"CVE-2019-13118"},"products":["n/a"],"published":"2019-10-07","related":[{"cvss_score":8.1,"headline":"Null dereference in n/a","id":"CVE-2018-16522","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2018-16525","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2018-16526","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2018-16528","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":8.1,"headline":"Integer overflow in n/a","id":"CVE-2018-16601","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":7.4,"headline":"Denial of service in n/a","id":"CVE-2018-16523","kev_date_added":null,"published":"2018-12-06"}],"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-04","vendors":["n/a"]},"summary":"An attacker with MQTT publish authorization can trigger memory leakage in Amazon FreeRTOS by sending malformed packets, exposing arbitrary memory contents.","url":"https://insights.sbomify.com/CVE-2019-13120/"}