Skip to content
Fencer Intel
medium 6.8

CVE-2013-4660 json

Deserialization Code Execution in js-yaml

published 13y ago modified 4mo ago also GHSA-xxvw-45rp-3mj2 , EUVD-2017-0338

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
17.2%
EPSS 17.2% chance of exploitation in 30 days, percentile 97%
public exploits
2
Metasploit and Exploit-DB

Summary

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.

Patch / fix

  • npm js-yaml 2.0.5

Is CVE-2013-4660 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/multi/fileformat/nodejs_js_yaml_load_code_exec)
  2. Published

Exploit prediction

17.19% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
npm js-yaml
<2.0.5
2.0.5

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.