{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-34455 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-34455 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-34455 is a high-severity vulnerability in n/a, published on 3 May 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-34455 and fix it if it is affected.\n\nWhat it is: CVE-2024-34455 is a high-severity vulnerability in n/a, published on 3 May 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-34455 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-34455/ (Markdown: https://insights.sbomify.com/CVE-2024-34455/index.md)","id":"CVE-2024-34455","markdown":"https://insights.sbomify.com/CVE-2024-34455/index.md","name":"CVE-2024-34455","record":{"aliases":["GHSA-m6xf-rg25-42wc"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Buildroot embedded OS","requires_auth":"none","summary":"Missing sticky bit on /dev/shm allows unauthorized users to read or modify shared memory data in Buildroot systems.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","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-276","name":"Incorrect Default Permissions"}],"description":"Buildroot before 0b2967e lacks the sticky bit for the /dev/shm directory. A fix was released in 2024.02.2.","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":"Misconfiguration in n/a","id":"CVE-2024-34455","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2024"},"n_packages":0,"n_references":5,"next":{"headline":"Apache StreamPark IDOR Vulnerability","id":"CVE-2024-34457"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2024-34454"},"products":["n/a"],"published":"2024-05-03","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Missing sticky bit on /dev/shm allows unauthorized users to read or modify shared memory data in Buildroot systems.","url":"https://insights.sbomify.com/CVE-2024-34455/"}