What is CVE-2022-41713?

CVE-2022-41713 is a medium-severity security vulnerability in deep-object-diff (npm), affecting versions >= 1.1.6, < 1.1.9. It is fixed in 1.1.9.

How severe is CVE-2022-41713?

CVE-2022-41713 has a CVSS score of 5.3 (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 deep-object-diff are affected by CVE-2022-41713?

deep-object-diff (npm) versions >= 1.1.6, < 1.1.9 is affected.

Is there a fix for CVE-2022-41713?

Yes. CVE-2022-41713 is fixed in 1.1.9. Upgrade to this version or later.

Is CVE-2022-41713 exploitable, and should I be worried?

Whether CVE-2022-41713 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-2022-41713 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-2022-41713 in deep-object-diff

Q: How severe is CVE-2022-41713?

CVE-2022-41713 has a CVSS score of 5.3 (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 deep-object-diff are affected by CVE-2022-41713?

deep-object-diff (npm) versions >= 1.1.6, < 1.1.9 is affected.

Q: Is there a fix for CVE-2022-41713?

Yes. CVE-2022-41713 is fixed in 1.1.9. Upgrade to this version or later.

Q: Is CVE-2022-41713 exploitable, and should I be worried?

Whether CVE-2022-41713 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-2022-41713 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-2022-41713?

Upgrade deep-object-diff to 1.1.9 or later.

Summary

deep-object-diff vulnerable to Prototype Pollution

deep-object-diff before version 1.1.6 allows an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the __proto__ property to be edited. This issue was fixed in version 1.1.9.

Impact

CVE-2022-41713 has a CVSS score of 5.3 (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 (1.1.9); upgrading removes the vulnerable code path.

Affected versions

deep-object-diff (>= 1.1.6, < 1.1.9)

Security releases

deep-object-diff → 1.1.9 (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 deep-object-diff to 1.1.9 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-2022-41713? CVE-2022-41713 is a medium-severity security vulnerability in deep-object-diff (npm), affecting versions >= 1.1.6, < 1.1.9. It is fixed in 1.1.9.
How severe is CVE-2022-41713? CVE-2022-41713 has a CVSS score of 5.3 (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 deep-object-diff are affected by CVE-2022-41713? deep-object-diff (npm) versions >= 1.1.6, < 1.1.9 is affected.
Is there a fix for CVE-2022-41713? Yes. CVE-2022-41713 is fixed in 1.1.9. Upgrade to this version or later.
Is CVE-2022-41713 exploitable, and should I be worried? Whether CVE-2022-41713 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-2022-41713 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-2022-41713? Upgrade deep-object-diff to 1.1.9 or later.