What is CVE-2020-36472?

CVE-2020-36472 is a medium-severity race condition vulnerability in max7301 (rust), affecting versions < 0.2.0. It is fixed in 0.2.0. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.

How severe is CVE-2020-36472?

CVE-2020-36472 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of max7301 are affected by CVE-2020-36472?

max7301 (rust) versions < 0.2.0 is affected.

Is there a fix for CVE-2020-36472?

Yes. CVE-2020-36472 is fixed in 0.2.0. Upgrade to this version or later.

Is CVE-2020-36472 exploitable, and should I be worried?

Whether CVE-2020-36472 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 CVE-2020-36472 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.

CVE-2020-36472 in max7301

Q: How severe is CVE-2020-36472?

CVE-2020-36472 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of max7301 are affected by CVE-2020-36472?

max7301 (rust) versions < 0.2.0 is affected.

Q: Is there a fix for CVE-2020-36472?

Yes. CVE-2020-36472 is fixed in 0.2.0. Upgrade to this version or later.

Q: Is CVE-2020-36472 exploitable, and should I be worried?

Whether CVE-2020-36472 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 CVE-2020-36472 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.

Q: How do I fix CVE-2020-36472?

Upgrade max7301 to 0.2.0 or later.

Summary

Data races in max7301

The ImmediateIO and TransactionalIO types implement Sync for all contained
Expander<EI> types regardless of if the Expander itself is safe to use
across threads.

As the IO types allow retrieving the Expander, this can lead to non-thread
safe types being sent across threads as part of the Expander leading to data
races.

Impact

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

CVE-2020-36472 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.2.0); upgrading removes the vulnerable code path.

Affected versions

max7301 (< 0.2.0)

Security releases

max7301 → 0.2.0 (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 max7301 to 0.2.0 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 CVE-2020-36472? CVE-2020-36472 is a medium-severity race condition vulnerability in max7301 (rust), affecting versions < 0.2.0. It is fixed in 0.2.0. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
How severe is CVE-2020-36472? CVE-2020-36472 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of max7301 are affected by CVE-2020-36472? max7301 (rust) versions < 0.2.0 is affected.
Is there a fix for CVE-2020-36472? Yes. CVE-2020-36472 is fixed in 0.2.0. Upgrade to this version or later.
Is CVE-2020-36472 exploitable, and should I be worried? Whether CVE-2020-36472 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 CVE-2020-36472 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 CVE-2020-36472? Upgrade max7301 to 0.2.0 or later.