{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39274 exists.","fix":"No fix has been published for CVE-2022-39274 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39274 is a high-severity memory corruption vulnerability in Lora-net LoRaMac-node, 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-39274 and fix it if it is affected.\n\nWhat it is: CVE-2022-39274 is a high-severity memory corruption vulnerability in Lora-net LoRaMac-node, published on 6 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39274 exists.\n\nAffected product: Lora-net LoRaMac-node. 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-39274/ (Markdown: https://insights.sbomify.com/CVE-2022-39274/index.md)","id":"CVE-2022-39274","markdown":"https://insights.sbomify.com/CVE-2022-39274/index.md","name":"CVE-2022-39274","record":{"aliases":["GHSA-7vv8-73pc-63c2"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"LoRa network node","requires_auth":"low_privilege","summary":"An attacker can trigger a buffer overflow in LoRaMac-node via crafted radio frames, potentially leading to remote code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"loramac-node","vendor":"semtech"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-193","name":"Off-by-one Error"},{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"LoRaMac-node is a reference implementation and documentation of a LoRa network node. Versions of LoRaMac-node prior to 4.7.0 are vulnerable to a buffer overflow. Improper size validation of the incoming radio frames can lead to an 65280-byte out-of-bounds write. The function `ProcessRadioRxDone` implicitly expects incoming radio frames to have at least a payload of one byte or more. An empty payload leads to a 1-byte out-of-bounds read of user controlled content when the payload buffer is reused. This allows an attacker to craft a FRAME_TYPE_PROPRIETARY frame with size -1 which results in an 65280-byte out-of-bounds memcopy likely with partially controlled attacker data. Corrupting a large part if the data section is likely to cause a DoS. If the large out-of-bounds write does not immediately crash the attacker may gain control over the execution due to now controlling large parts of the data section. Users are advised to upgrade either by updating their package or by manually applying the patch commit `e851b079`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Buffer Overflow in `ProcessRadioRxDone` in LoRaMac-node","id":"CVE-2022-39274","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Improper object type validation in saleor","id":"CVE-2022-39275"},"packages":[],"prev":{"headline":"Default OAuth Authorization Server secret in FlyteAdmin","id":"CVE-2022-39273"},"products":["LoRaMac-node"],"published":"2022-10-06","related":[{"cvss_score":5,"headline":"Potential Buffer Overflow in LoRaMac-node","id":"CVE-2020-11068","kev_date_added":null,"published":"2020-06-23"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["Lora-net"]},"summary":"An attacker can trigger a buffer overflow in LoRaMac-node via crafted radio frames, potentially leading to remote code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2022-39274/"}