{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-21739 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-21739 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-21739 is a medium-severity missing authorization vulnerability in n/a, published on 25 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-21739 and fix it if it is affected.\n\nWhat it is: CVE-2024-21739 is a medium-severity missing authorization vulnerability in n/a, published on 25 Jun 2024. 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-2024-21739 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-2024-21739/ (Markdown: https://insights.sbomify.com/CVE-2024-21739/index.md)","id":"CVE-2024-21739","markdown":"https://insights.sbomify.com/CVE-2024-21739/index.md","name":"CVE-2024-21739","record":{"aliases":["GHSA-4xjp-m233-hj66"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"APM32 microcontroller","requires_auth":"none","summary":"Attackers can bypass access controls on Geehy APM32F103 series microcontrollers, potentially gaining unauthorized access to device functions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"Geehy APM32F103CCT6, APM32F103RCT6, APM32F103RCT7, and APM32F103VCT6 devices have Incorrect Access Control.","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":"Missing authorization in n/a","id":"CVE-2024-21739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2024-21740"},"packages":[],"prev":{"headline":"Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver ABAP Application Server and ABAP Platform","id":"CVE-2024-21738"},"products":["n/a"],"published":"2024-06-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-07","vendors":["n/a"]},"summary":"Attackers can bypass access controls on Geehy APM32F103 series microcontrollers, potentially gaining unauthorized access to device functions.","url":"https://insights.sbomify.com/CVE-2024-21739/"}