Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

CVE-2013-4660

CVE-2013-4660 is a Improper Input Validation vulnerability in nodeca js-yaml. 3 public exploit references exist, so weaponization risk is real. O3 Security detects and blocks CVE-2013-4660 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

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…

Published
Jun 28, 2013
Updated
Jun 16, 2026
Affected
0 pkgs
Patched
None yet
Exploits
3 known

EPSS Exploitation Probability

via FIRST.org ↗
17.2%probability of exploitation in next 30 days
Moderate Risk97th percentile0.00%
2.99%28.2%53.5%78.7%64.5%17.2%Jan 26May 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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.

Affected Products

1 product · 20 configurations
Application
js-yamlnodeca
≤ 2.0.4
19 versions
0.2.00.2.10.2.20.3.00.3.10.3.20.3.30.3.40.3.50.3.60.3.71.0.0
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-28655localmultiple✓ Verified

Nodejs - 'js-yaml load()' Code Exec (Metasploit)

by Metasploit · Sep 30, 2013

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every nodeca js-yaml deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

  2. Remediation status

    No patch has shipped for CVE-2013-4660 yet — track the nodeca js-yaml advisory for a fixed release and apply the workarounds below in the meantime.

  3. Mitigate without a patch

    Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

  4. How O3 protects you

    O3 detects and blocks CVE-2013-4660 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2013-4660. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Runtime Protection

Is CVE-2013-4660 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2013-4660 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.