What is CVE-2021-4264?

CVE-2021-4264 is a high-severity code injection vulnerability in dustjs-linkedin (npm), affecting versions < 3.0.0. It is fixed in 3.0.0. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2021-4264?

CVE-2021-4264 has a CVSS score of 8.8 (High). 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 dustjs-linkedin are affected by CVE-2021-4264?

dustjs-linkedin (npm) versions < 3.0.0 is affected.

Is there a fix for CVE-2021-4264?

Yes. CVE-2021-4264 is fixed in 3.0.0. Upgrade to this version or later.

Is CVE-2021-4264 exploitable, and should I be worried?

Whether CVE-2021-4264 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-2021-4264 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-2021-4264 in dustjs-linkedin

Q: How severe is CVE-2021-4264?

CVE-2021-4264 has a CVSS score of 8.8 (High). 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 dustjs-linkedin are affected by CVE-2021-4264?

dustjs-linkedin (npm) versions < 3.0.0 is affected.

Q: Is there a fix for CVE-2021-4264?

Yes. CVE-2021-4264 is fixed in 3.0.0. Upgrade to this version or later.

Q: Is CVE-2021-4264 exploitable, and should I be worried?

Whether CVE-2021-4264 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-2021-4264 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-2021-4264?

Upgrade dustjs-linkedin to 3.0.0 or later.

Summary

dustjs-linkedin vulnerable to Prototype Pollution

A vulnerability was found in LinkedIn dustjs prior to version 3.0.0 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation leads to improperly controlled modification of object prototype attributes ('prototype pollution'). The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 3.0.0 can address this issue. The name of the patch is ddb6523832465d38c9d80189e9de60519ac307c3. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-216464.

Impact

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2021-4264 has a CVSS score of 8.8 (High). The vector is network-reachable, 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 (3.0.0); upgrading removes the vulnerable code path.

Affected versions

dustjs-linkedin (< 3.0.0)

Security releases

dustjs-linkedin → 3.0.0 (npm)

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 dustjs-linkedin to 3.0.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-2021-4264? CVE-2021-4264 is a high-severity code injection vulnerability in dustjs-linkedin (npm), affecting versions < 3.0.0. It is fixed in 3.0.0. Untrusted input is evaluated as executable code within the application's runtime environment.
How severe is CVE-2021-4264? CVE-2021-4264 has a CVSS score of 8.8 (High). 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 dustjs-linkedin are affected by CVE-2021-4264? dustjs-linkedin (npm) versions < 3.0.0 is affected.
Is there a fix for CVE-2021-4264? Yes. CVE-2021-4264 is fixed in 3.0.0. Upgrade to this version or later.
Is CVE-2021-4264 exploitable, and should I be worried? Whether CVE-2021-4264 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-2021-4264 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-2021-4264? Upgrade dustjs-linkedin to 3.0.0 or later.