{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-42130 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-42130 is a vulnerability, published on 30 Jul 2024."},"fix_prompt":"Check this codebase for CVE-2024-42130 and fix it if it is affected.\n\nWhat it is: CVE-2024-42130 is a vulnerability, published on 30 Jul 2024. \nExploitation: There is no known exploitation of CVE-2024-42130 in the wild and no public exploit code.\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-42130/ (Markdown: https://insights.sbomify.com/CVE-2024-42130/index.md)","id":"CVE-2024-42130","markdown":"https://insights.sbomify.com/CVE-2024-42130/index.md","name":"CVE-2024-42130","record":{"aliases":["BELL-CVE-2024-42130","GHSA-m4wm-24vm-w63j","ROOT-OS-DEBIAN-11-CVE-2024-42130","UBUNTU-CVE-2024-42130"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-42130","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2024"},"n_packages":0,"n_references":0,"next":{"headline":"mm: avoid overflows in dirty throttling logic","id":"CVE-2024-42131"},"packages":[],"prev":{"headline":"leds: mlxreg: Use devm_mutex_init() for mutex initialization","id":"CVE-2024-42129"},"products":[],"published":"2024-07-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2026-01-31","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2024-42130/"}