{"answers":{"affected":"3 open source packages ship an affected version, including mnl.","exploited":"There is no known exploitation of GHSA-585q-cm62-757j in the wild and no public exploit code.","fix":"Upgrade mnl to 0.3.1 or later.","what":"GHSA-585q-cm62-757j is a vulnerability in mnl, published on 18 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-585q-cm62-757j and fix it if it is affected.\n\nWhat it is: GHSA-585q-cm62-757j is a vulnerability in mnl, published on 18 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-585q-cm62-757j in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mnl (crates.io): affected all versions; fixed in 0.3.1\n- mnl (crates.io): affected all versions; fixed in 0.3.1\n- mnl (crates.io): affected from 0.0.0-0; fixed in 0.3.1\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/GHSA-585q-cm62-757j/ (Markdown: https://insights.sbomify.com/GHSA-585q-cm62-757j/index.md)","id":"GHSA-585q-cm62-757j","markdown":"https://insights.sbomify.com/GHSA-585q-cm62-757j/index.md","name":"GHSA-585q-cm62-757j","record":{"aliases":["RUSTSEC-2025-0142"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust Netlink library","requires_auth":"none","summary":"An attacker can cause a segmentation fault or read unmapped memory by sending a malformed Netlink message to applications using the mnl library.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The function `mnl::cb_run` is marked as safe but exhibits unsound behavior when processing malformed Netlink message buffers.\n\nPassing a crafted byte slice to `mnl::cb_run` can trigger memory violations. The function does not sufficiently validate the input buffer structure before processing, leading to out-of-bounds reads.\n\nThis vulnerability allows an attacker to cause a Denial of Service (segmentation fault) or potentially read unmapped memory by providing a malformed Netlink message.\n\nThe underlying issue is a bug in `libmnl` where during validation `nlh-\u003enlmsg_len` is cast to an `int` and becomes negative if `nlmsg_len` is greater than `INT_MAX`. This causes the validation to succeed even if the buffer is too small for the message. This has been fixed in `libmnl` but still affects version 1.0.5.\n\nThe issue in `mnl` was fixed in commit `cd51bdc` by checking the validity of netlink messages passed to `mnl::cb_run`.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Segmentation fault and invalid memory read in `mnl::cb_run`","id":"GHSA-585q-cm62-757j","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"integer_overflow","year":"2025"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.3.1"],"introduced":["0"],"last_affected":[],"package":"mnl","purl":null,"source":"GHSA-585q-cm62-757j"},{"ecosystem":"crates.io","fixed":["0.3.1"],"introduced":["0"],"last_affected":[],"package":"mnl","purl":"pkg:cargo/mnl","source":"GHSA-585q-cm62-757j"},{"ecosystem":"crates.io","fixed":["0.3.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"mnl","purl":"pkg:cargo/mnl","source":"RUSTSEC-2025-0142"}],"products":null,"published":"2025-10-18","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can cause a segmentation fault or read unmapped memory by sending a malformed Netlink message to applications using the mnl library.","url":"https://insights.sbomify.com/GHSA-585q-cm62-757j/"}