Skip to content
Fencer Intel
medium 5.0

CVE-2013-1654 json

Puppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, and Puppet Enterprise 2.7.x before 2.7.2, does not properly negotiate the SSL protocol b…

published 13y ago modified 4mo ago also EUVD-2013-1685

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.9%
EPSS 2.9% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

Puppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, and Puppet Enterprise 2.7.x before 2.7.2, does not properly negotiate the SSL protocol between client and master, which allows remote attackers to conduct SSLv2 downgrade attacks against SSLv3 sessions via unspecified vectors.

Patch / fix

  • puppet Debian 11 2.7.18-3

debian advisories DEBIAN-CVE-2013-1654

  • puppet openstack 2 2.6.18-1.el6ost
  • puppet-server openstack 2 2.6.18-1.el6ost

red hat advisories RHSA-2013:0710

Is CVE-2013-1654 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2013-1654 updated cvss 4.3

Puppet: SSL protocol downgrade

  • Red Hat Enterprise MRG 1 puppet Red Hat Subscription Asset Manager puppet
    affected: no fix available
  • Red Hat OpenStack Folsom puppet 2.6.18-1.el6ost, puppet-server 2.6.18-1.el6ost
    fixed: vendor fix RHSA-2013:0710

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

2.95% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

References

Sources

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.