swagger-parser vulnerabilities and fixes

Q: How do I fix swagger-parser vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Q: Is swagger-parser being exploited right now?

None of the tracked swagger-parser CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Q: Which swagger-parser CVE should I patch first?

CVE-2017-1000208 currently ranks highest (50/100): A vulnerability in Swagger-Parser's (version <= 1.0.30) yaml parsing functionality results in arbitrary code b.

Recent CVEs affecting swagger-parser, with upgrade or downgrade steps. 2 tracked.

Also searched as: swagger parser.

swagger-parser has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2017-11-27. Highest priority: CVE-2017-1000208 (score 50/100).

CVE-2017-1000208 HIGH 8.8 UPGRADE UPGRADE A vulnerability in Swagger-Parser's (version <= 1.0.30) yaml parsing functionality results in arbitrary code b
CVE-2017-1000207 HIGH 8.8 UPGRADE UPGRADE A vulnerability in Swagger-Parser's version <= 1.0.30 and Swagger codegen version <= 2.2.2 yaml parsing functi

FAQ

How do I fix swagger-parser vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is swagger-parser being exploited right now?

None of the tracked swagger-parser CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which swagger-parser CVE should I patch first?

CVE-2017-1000208 currently ranks highest (50/100): A vulnerability in Swagger-Parser's (version <= 1.0.30) yaml parsing functionality results in arbitrary code b.

← Back to latest CVEs