What is CVE-2017-20187?

CVE-2017-20187 is a low-severity security vulnerability in floriangaerber/magnesium (composer), affecting versions < 0.3.1. It is fixed in 0.3.1.

How severe is CVE-2017-20187?

CVE-2017-20187 has a CVSS score of 3.5 (Low). 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 floriangaerber/magnesium are affected by CVE-2017-20187?

floriangaerber/magnesium (composer) versions < 0.3.1 is affected.

Is there a fix for CVE-2017-20187?

Yes. CVE-2017-20187 is fixed in 0.3.1. Upgrade to this version or later.

Is CVE-2017-20187 exploitable, and should I be worried?

Whether CVE-2017-20187 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-2017-20187 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-2017-20187 in floriangaerber/magnesium

Q: How severe is CVE-2017-20187?

CVE-2017-20187 has a CVSS score of 3.5 (Low). 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 floriangaerber/magnesium are affected by CVE-2017-20187?

floriangaerber/magnesium (composer) versions < 0.3.1 is affected.

Q: Is there a fix for CVE-2017-20187?

Yes. CVE-2017-20187 is fixed in 0.3.1. Upgrade to this version or later.

Q: Is CVE-2017-20187 exploitable, and should I be worried?

Whether CVE-2017-20187 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-2017-20187 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-2017-20187?

Upgrade floriangaerber/magnesium to 0.3.1 or later.

Summary

Magnesium-PHP Injection vulnerability

** UNSUPPORTED WHEN ASSIGNED ** ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in Magnesium-PHP up to 0.3.0. It has been classified as problematic. Affected is the function formatEmailString of the file src/Magnesium/Message/Base.php. The manipulation of the argument email/name leads to injection. Upgrading to version 0.3.1 is able to address this issue. The patch is identified as 500d340e1f6421007413cc08a8383475221c2604. It is recommended to upgrade the affected component. VDB-244482 is the identifier assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Impact

CVE-2017-20187 has a CVSS score of 3.5 (Low). The vector is reachable from an adjacent network, low 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.3.1); upgrading removes the vulnerable code path.

Affected versions

floriangaerber/magnesium (< 0.3.1)

Security releases

floriangaerber/magnesium → 0.3.1 (composer)

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 floriangaerber/magnesium 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 CVE-2017-20187? CVE-2017-20187 is a low-severity security vulnerability in floriangaerber/magnesium (composer), affecting versions < 0.3.1. It is fixed in 0.3.1.
How severe is CVE-2017-20187? CVE-2017-20187 has a CVSS score of 3.5 (Low). 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 floriangaerber/magnesium are affected by CVE-2017-20187? floriangaerber/magnesium (composer) versions < 0.3.1 is affected.
Is there a fix for CVE-2017-20187? Yes. CVE-2017-20187 is fixed in 0.3.1. Upgrade to this version or later.
Is CVE-2017-20187 exploitable, and should I be worried? Whether CVE-2017-20187 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-2017-20187 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-2017-20187? Upgrade floriangaerber/magnesium to 0.3.1 or later.