CVE-2014-3250 json
The default vhost configuration file in Puppet before 3.6.2 does not include the SSLCARevocationCheck directive, which might allow remote a…
published 2017-12-11 8 y ago modified 2026-06-17 4 mo ago also EUVD-2014-3263
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
The default vhost configuration file in Puppet before 3.6.2 does not include the SSLCARevocationCheck directive, which might allow remote attackers to obtain sensitive information via a revoked certificate when a Puppet master runs with Apache 2.4.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-3250 updated cvss 5.0
puppet: certificates could be honored even when revoked
-
Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) puppet Red Hat OpenStack Platform 3 puppet Red Hat OpenStack Platform 4 puppetaffected: no fix planned “Will not fix”
-
Red Hat Satellite 6 puppet, puppet-serveraffected: no fix available
-
Red Hat Subscription Asset Manager ruby193-puppetnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
bugzilla.redhat.com
/show_bug.cgi?id=1101347
issue-tracking, patch, third-party-advisory
-
puppet.com
/security/cve/CVE-2014-3250
vendor-advisory
Sources
- CVE List CVE-2014-3250
- NVD CVE-2014-3250
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.