How severe is CVE-2017-16763?

CVE-2017-16763 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-16763 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-16763?

CVE-2017-16763 affects Confire Project Confire. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-16763?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2017-16763 published?

CVE-2017-16763 was published on 2017-11-10 and last updated on 2026-06-17.

CVE-2017-16763

CVE-2017-16763 is a critical-severity vulnerability in Confire Project Confire with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 4% (90th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Confire Project Confire
Published: 2017-11-10
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2017-16763?: 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.
How severe is CVE-2017-16763?: CVE-2017-16763 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-16763 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-16763?: CVE-2017-16763 affects Confire Project Confire. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-16763?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2017-16763 published?: CVE-2017-16763 was published on 2017-11-10 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:confire_project:confire:0.2.0:*:*:*:*:*:*:*