CVE-2020-7679: Improperly Controlled Modification of Dynamically-Determined Object Attributes in casperjs

casperjs Updated 02 Oct 2025

Summary

17/05/2021
No i
High
7.3

CVE-2020-7679: Improperly Controlled Modification of Dynamically-Determined Object Attributes in casperjs. Affects casperjs versions < 1.1.4. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

CasperJS is an open-source navigation scripting and testing utility for PhantomJS and SlimerJS. It provides a high-level API for automating web browsing activities, such as form submission, clicking links, and capturing screenshots. CasperJS is vulnerable to Prototype Pollution, specifically in the mergeObjects utility function.

Vulnerability Detail

The mergeObjects utility function in CasperJS is susceptible to Prototype Pollution. This vulnerability allows an attacker to modify the prototype of an object, leading to the modification of existing or creation of new properties and methods. By manipulating the prototype chain, an attacker can execute arbitrary code, escalate privileges, or cause denial of service. The impact of this vulnerability can be severe, depending on the context in which CasperJS is used.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update CasperJS to a version that includes a patch for the Prototype Pollution issue. The latest version of CasperJS at the time of writing is 1.1.4, which is not affected by this vulnerability. Upgrading to this version or any subsequent versions that address the issue will mitigate the risk.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. It is crucial to update CasperJS to a patched version to ensure the security of the application.

Conclusion

In conclusion, CasperJS is vulnerable to Prototype Pollution in the mergeObjects utility function. This vulnerability can have severe consequences, including arbitrary code execution and privilege escalation. It is crucial to update CasperJS to a patched version, such as 1.1.4, to mitigate the risk. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for casperjs →

Share this vulnerability

FAQ

CasperJS is an open-source navigation scripting and testing utility for PhantomJS and SlimerJS. It provides a high-level API for automating web browsing activities.

Prototype Pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to the modification of existing or creation of new properties and methods.

The consequences of this vulnerability can vary depending on the context in which CasperJS is used. It can allow an attacker to execute arbitrary code, escalate privileges, or cause denial of service.

Yes, updating CasperJS to a version that includes a patch for the Prototype Pollution issue will fix this vulnerability. The latest version, 1.1.4, is not affected by this vulnerability.

For more information about CasperJS and this vulnerability, you can refer to the official documentation and the advisory provided by the GitHub Security Advisory Database.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update CasperJS to a version that includes a patch for the Prototype Pollution issue. The latest version of CasperJS at the time of writing is 1.1.4, which is not affected by this vulnerability. Upgrading to this version or any subsequent versions that address the issue will mitigate the risk.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.