High

RCE via YAML Deserialization in Swagger-Parser and Swagger Codegen (SnakeYaml)

IdentifiersCVE-2017-1000207CWE-502· Deserialization of Untrusted Data

CVE-2017-1000207 is a remote code execution vulnerability in Swagger-Parser (<= 1.0.30) and Swagger Codegen (<= 2.2.2) due to unsafe YAML deserialization using the SnakeYaml library. When a maliciously crafted YAML OpenAPI specification is parsed (notably via the 'generate' and 'validate' commands), arbitrary Java classes can be instantiated, allowing attackers to execute arbitrary code. The vulnerability is triggered when user-controlled YAML input is passed to yaml.load(), which can be abused to load and execute attacker-hosted Java classes via constructs such as javax.script.ScriptEngineManager and java.net.URLClassLoader.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to achieve remote code execution on the server running Swagger-Parser or Swagger Codegen by submitting a malicious YAML file. The attacker can execute arbitrary Java code, potentially leading to full system compromise, data exfiltration, or lateral movement within the environment. The attack requires the ability to submit YAML input and host malicious Java class files on a remote server.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict or sanitize YAML input to prevent attacker-controlled data from reaching the deserialization routines. Use SnakeYaml's safeLoad() instead of load() to limit deserialization to standard YAML types. Employ network controls to prevent the application from reaching attacker-controlled servers for class loading, and monitor for suspicious outbound connections.

Remediation

Patch, then assume compromise.

Upgrade Swagger-Parser to a version > 1.0.30 and Swagger Codegen to a version > 2.2.2, where the YAML parsing functionality has been secured. Additionally, ensure that SnakeYaml is used in safe mode or with type restrictions to prevent arbitrary class instantiation. Avoid passing untrusted YAML input directly to yaml.load().

PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

SwaggerSwagger-Codegenapplication

SwaggerSwagger-Parserapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity