high
7.5
CWE
20
Advisory Published
Advisory Published
Updated

CVE-2013-3567: Input Validation

First published: Mon Aug 19 2013(Updated: )

Puppet 2.7.x before 2.7.22 and 3.2.x before 3.2.2, and Puppet Enterprise before 2.8.2, deserializes untrusted YAML, which allows remote attackers to instantiate arbitrary Ruby classes and execute arbitrary code via a crafted REST API call.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
rubygems/puppet>=3.2.0<3.2.2
3.2.2
rubygems/puppet>=2.7.0<2.7.22
2.7.22
Puppet=2.7.2
Puppet=2.7.10
Puppet=2.7.11
Puppet=2.7.12
Puppet=2.7.13
Puppet=2.7.14
Puppet=2.7.16
Puppet=2.7.17
Puppet=2.7.18
Puppet=2.7.21
Puppet=3.2.1
Puppet=2.7.0
Puppet=2.7.1
Puppet=2.7.19
Puppet=2.7.20
Puppet=2.7.20-rc1
Puppet=3.2.0
Ubuntu=12.04
Ubuntu=12.10
Ubuntu=13.04
SUSE Linux Enterprise Desktop=11-sp3
SUSE Linux Enterprise Desktop=11.0-sp2
SUSE Linux Enterprise Server=11.0-sp2
SUSE Linux Enterprise Server=11.0-sp3
SUSE Linux Enterprise Server=11.0-sp3
Puppet Enterprise<=2.8.1
Puppet Enterprise=1.0
Puppet Enterprise=1.1
Puppet Enterprise=1.2.0
Puppet Enterprise=2.0.0
Puppet Enterprise=2.5.1
Puppet Enterprise=2.5.2
Puppet Enterprise=2.8.0
Puppet=1.0.0
Puppet=1.1.0
Puppet=1.2.0
Puppet=2.5.0
Puppet=2.6.0
Puppet=2.7.0
Puppet=2.7.1
Puppet=2.7.2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2013-3567?

    CVE-2013-3567 is considered a critical vulnerability due to the potential for remote code execution.

  • How do I fix CVE-2013-3567?

    To fix CVE-2013-3567, upgrade Puppet to version 2.7.22 or 3.2.2, or use a later version.

  • What versions of Puppet are affected by CVE-2013-3567?

    Affected versions include Puppet 2.7.x prior to 2.7.22, Puppet 3.2.x prior to 3.2.2, and Puppet Enterprise prior to 2.8.2.

  • What types of attacks can exploit CVE-2013-3567?

    CVE-2013-3567 can be exploited by sending a crafted REST API call that deserializes untrusted YAML.

  • How was CVE-2013-3567 discovered?

    CVE-2013-3567 was discovered through the identification of unsafe deserialization patterns in Puppet's handling of YAML.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203