{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34473 exists.","fix":"No fix has been published for CVE-2024-34473 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-34473 is a medium-severity vulnerability in n/a, published on 4 May 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-34473 and fix it if it is affected.\n\nWhat it is: CVE-2024-34473 is a medium-severity vulnerability in n/a, published on 4 May 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-34473 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-34473/ (Markdown: https://insights.sbomify.com/CVE-2024-34473/index.md)","id":"CVE-2024-34473","markdown":"https://insights.sbomify.com/CVE-2024-34473/index.md","name":"CVE-2024-34473","record":{"aliases":["GHSA-cxq3-mwqc-vjv7"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"O-RAN Near-RT RIC","requires_auth":"low_privilege","summary":"An attacker can disrupt service components by registering unintended message types during xApp registration in the O-RAN Near-RT RIC.","user_interaction":"not_required","vuln_class":"business_logic"},"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:H/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered in appmgr in O-RAN Near-RT RIC I-Release. An attacker could register an unintended RMR message type during xApp registration to disrupt other service components.","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":"Business logic in n/a","id":"CVE-2024-34473","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2024-34474"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2024-34472"},"products":["n/a"],"published":"2024-05-04","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":"partial"},"state":"PUBLISHED","updated":"2025-03-27","vendors":["n/a"]},"summary":"An attacker can disrupt service components by registering unintended message types during xApp registration in the O-RAN Near-RT RIC.","url":"https://insights.sbomify.com/CVE-2024-34473/"}