CVE-2017-16615

Name: CVE-2017-16615
Creator: NVD / NIST
Published: 2017-11-08T03:29:00.2+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 3.42%

Last modified Jun 17, 2026

CVE-2017-16615 is a vulnerability of currently unknown severity. An exploitable vulnerability exists in the YAML parsing functionality in the parse_yaml_query method in parser.py in MLAlchemy before 0.2.2. When processing YAML-Based queries for data, a YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. EPSS estimates a 3.42% chance of exploitation in the next 30 days.

Description

An exploitable vulnerability exists in the YAML parsing functionality in the parse_yaml_query method in parser.py in MLAlchemy before 0.2.2. When processing YAML-Based queries for data, a YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.

Metrics

EPSS Probability

3.42%

87.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Vendor	Product	Versions
Mlalchemy Project	Mlalchemy	0.1.1
Mlalchemy Project	Mlalchemy	0.1.2
Mlalchemy Project	Mlalchemy	0.1.3
Mlalchemy Project	Mlalchemy	0.2.0
Mlalchemy Project	Mlalchemy	0.2.1

References

https://github.com/thanethomson/MLAlchemy/commit/bc795757febdcce430d89f9d08f75c32d6989d3cIssue Tracking
https://github.com/thanethomson/MLAlchemy/issues/1Issue Tracking
https://joel-malwarebenchmark.github.io/blog/2017/11/08/cve-2017-16615-critical-restful-web-applications-vulnerability/Third Party Advisory
https://github.com/thanethomson/MLAlchemy/commit/bc795757febdcce430d89f9d08f75c32d6989d3cIssue Tracking
https://github.com/thanethomson/MLAlchemy/issues/1Issue Tracking
https://joel-malwarebenchmark.github.io/blog/2017/11/08/cve-2017-16615-critical-restful-web-applications-vulnerability/Third Party Advisory

Timeline

Published: Nov 8, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-16615?

How severe is CVE-2017-16615?

Severity scoring for CVE-2017-16615 is pending analysis. The EPSS model estimates a 3.42% probability of exploitation in the next 30 days.

How do I fix CVE-2017-16615?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-16615?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST