{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39209 exists.","fix":"No fix has been published for CVE-2024-39209 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-39209 is a medium-severity command injection vulnerability in n/a, published on 27 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-39209 and fix it if it is affected.\n\nWhat it is: CVE-2024-39209 is a medium-severity command injection vulnerability in n/a, published on 27 Jun 2024. 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-2024-39209 exists.\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-2024-39209/ (Markdown: https://insights.sbomify.com/CVE-2024-39209/index.md)","id":"CVE-2024-39209","markdown":"https://insights.sbomify.com/CVE-2024-39209/index.md","name":"CVE-2024-39209","record":{"aliases":["GHSA-f4x7-3x4m-rmvx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenWrt SMS tool","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands via the score parameter in the luci-app-sms-tool web interface.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"luci-app-sms-tool v1.9-6 was discovered to contain a command injection vulnerability via the score parameter.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2024-39209","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2024-39210"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2024-39208"},"products":["n/a"],"published":"2024-06-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via the score parameter in the luci-app-sms-tool web interface.","url":"https://insights.sbomify.com/CVE-2024-39209/"}