Swagger-Parser's up to 1.0.30 YAML Parser code

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability was found in Swagger-Parser's up to 1.0.30 and classified as critical. Affected by this issue is an unknown part of the component YAML Parser. The manipulation with an unknown input leads to a code vulnerability. Using CWE to declare the problem leads to CWE-17. Impacted is confidentiality, integrity, and availability. CVE summarizes:

A vulnerability in Swagger-Parser's (version <= 1.0.30) yaml parsing functionality results in arbitrary code being executed when a maliciously crafted yaml Open-API specification is parsed. This in particular, affects the 'generate' and 'validate' command in swagger-codegen (<= 2.2.2) and can lead to arbitrary code being executed when these commands are used on a well-crafted yaml specification.

The bug was discovered 11/16/2017. The weakness was released 11/17/2017 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2017-1000208 since 11/16/2017. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.




CPE 2.3info

CPE 2.2info


VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍


VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.3

VulDB Base Score: 6.3
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Class: Code
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍


Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Upgrade: github.com


11/16/2017 🔍
11/16/2017 +0 days 🔍
11/16/2017 +0 days 🔍
11/17/2017 +1 days 🔍
11/18/2017 +1 days 🔍
01/10/2023 +1879 days 🔍


Advisory: github.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-1000208 (🔍)


Created: 11/18/2017 08:50 AM
Updated: 01/10/2023 05:41 PM
Changes: 11/18/2017 08:50 AM (54), 12/08/2019 08:37 AM (2), 01/10/2023 05:41 PM (4)
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!