What is GHSA-585Q-CM62-757J?

GHSA-585Q-CM62-757J is a low-severity out-of-bounds read vulnerability in mnl (rust), affecting versions <= 0.3.0. It is fixed in 0.3.1. A read operation accesses a memory location beyond the intended buffer boundary.

Which versions of mnl are affected by GHSA-585Q-CM62-757J?

mnl (rust) versions <= 0.3.0 is affected.

Is there a fix for GHSA-585Q-CM62-757J?

Yes. GHSA-585Q-CM62-757J is fixed in 0.3.1. Upgrade to this version or later.

Is GHSA-585Q-CM62-757J exploitable, and should I be worried?

Whether GHSA-585Q-CM62-757J is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-585Q-CM62-757J is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-585Q-CM62-757J in mnl

Q: Which versions of mnl are affected by GHSA-585Q-CM62-757J?

mnl (rust) versions <= 0.3.0 is affected.

Q: Is there a fix for GHSA-585Q-CM62-757J?

Yes. GHSA-585Q-CM62-757J is fixed in 0.3.1. Upgrade to this version or later.

Q: Is GHSA-585Q-CM62-757J exploitable, and should I be worried?

Whether GHSA-585Q-CM62-757J is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-585Q-CM62-757J is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Summary

mnl has segmentation fault and invalid memory read in mnl::cb_run

The function mnl::cb_run is marked as safe but exhibits unsound behavior when processing malformed Netlink message buffers.

Passing 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.

This vulnerability allows an attacker to cause a Denial of Service (segmentation fault) or potentially read unmapped memory by providing a malformed Netlink message.

Impact

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

Affected versions

mnl (<= 0.3.0)

Security releases

mnl → 0.3.1 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade mnl to 0.3.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-585Q-CM62-757J? GHSA-585Q-CM62-757J is a low-severity out-of-bounds read vulnerability in mnl (rust), affecting versions <= 0.3.0. It is fixed in 0.3.1. A read operation accesses a memory location beyond the intended buffer boundary.
Which versions of mnl are affected by GHSA-585Q-CM62-757J? mnl (rust) versions <= 0.3.0 is affected.
Is there a fix for GHSA-585Q-CM62-757J? Yes. GHSA-585Q-CM62-757J is fixed in 0.3.1. Upgrade to this version or later.
Is GHSA-585Q-CM62-757J exploitable, and should I be worried? Whether GHSA-585Q-CM62-757J is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-585Q-CM62-757J is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-585Q-CM62-757J? Upgrade mnl to 0.3.1 or later.