First published: Fri Jun 28 2013(Updated: )
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, which allows remote attackers to execute arbitrary code via a crafted string that triggers an eval operation.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
libyaml | <=2.0.4 | |
libyaml | =0.2.0 | |
libyaml | =0.2.1 | |
libyaml | =0.2.2 | |
libyaml | =0.3.0 | |
libyaml | =0.3.1 | |
libyaml | =0.3.2 | |
libyaml | =0.3.3 | |
libyaml | =0.3.4 | |
libyaml | =0.3.5 | |
libyaml | =0.3.6 | |
libyaml | =0.3.7 | |
libyaml | =1.0.0 | |
libyaml | =1.0.1 | |
libyaml | =1.0.2 | |
libyaml | =1.0.3 | |
libyaml | =2.0.0 | |
libyaml | =2.0.1 | |
libyaml | =2.0.2 | |
libyaml | =2.0.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-4660 is classified as a critical vulnerability due to its ability to execute arbitrary code remotely.
To mitigate CVE-2013-4660, update the JS-YAML module to version 2.0.5 or higher.
CVE-2013-4660 can be exploited through crafted strings that trigger an eval operation leading to remote code execution.
CVE-2013-4660 affects all versions of JS-YAML prior to 2.0.5.
The primary workaround for CVE-2013-4660 is to avoid using the unsafe !!js/function tag in YAML input.