Not ratedCVE-2013-1640

Puppet: Code Execution (CVE-2013-1640)

Published 20.03.2013Sources: CVE.org

What is affected, what to do

The (1) template and (2) inline_template functions in the master server in Puppet before 2.6.18, 2.7.x before 2.7.21, and 3.1.x before 3.1.1, and Puppet Enterprise before 1.2.7 and 2.7.x before 2.7.2 allows remote authenticated users to execute arbitrary code via a crafted catalog request.

Update Puppet to version 2.6.18, Puppet to version 2.7.21, Puppet Enterprise to version 1.2.7.

Affected: Puppet lt *..2.6.18
Puppet lt 2.7.0..2.7.21
Puppet eq 3.1.0..3.1.0
Puppet Enterprise lt *..1.2.7
Puppet Enterprise eq 2.7.0..2.7.0
Puppet Enterprise eq 2.7.1..2.7.1
Canonical Ubuntu Linux eq 11.10..11.10
Canonical Ubuntu Linux eq 12.04..12.04
Canonical Ubuntu Linux eq 12.10..12.10
Fixed in: Puppet 2.6.18
Puppet 2.7.21
Puppet Enterprise 1.2.7

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

—

Priority

No value is available for this vulnerability.

—

CVSS v3

No value is available for this vulnerability.

4.9 %

EPSS score

Moderate — model estimates 1-10% exploitation likelihood.

Source: FIRST EPSS, percentile 92.1

Show all metrics

Severity: Not rated
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 67.90 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: no public PoC known
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 4.9 %; Moderate — model estimates 1-10% exploitation likelihood.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 92.1; Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: —
Published: 20.03.2013

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

Source: NVD (NIST), cvelistv5

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
puppet	puppet	`3.1.0` `< 2.6.18` `2.7.0 – < 2.7.21`	— `2.6.18` `2.7.21`
puppet	puppet_enterprise	`< 1.2.7` `2.7.1` `2.7.0`	`1.2.7` — —

Vendors and products

Affected operating systems

Affected operating systems

Linux	canonical	ubuntu_linux	`11.10`
Linux	canonical	ubuntu_linux	`12.04`
Linux	canonical	ubuntu_linux	`12.10`

References & sources

lists.opensuse.orgSUSE-SU-2013:0618Vendor advisory, x_refsource_SUSE, Third-party advisory
rhn.redhat.comRHSA-2013:0710Vendor advisory, x_refsource_REDHAT, Third-party advisory
debian.orgDSA-2643Vendor advisory, x_refsource_DEBIAN, Third-party advisory
secunia.com52596Third-party advisory, x_refsource_SECUNIA, Third-party advisory
ubuntu.comUSN-1759-1Vendor advisory, x_refsource_UBUNTU, Third-party advisory
lists.opensuse.orgopenSUSE-SU-2013:0641Vendor advisory, x_refsource_SUSE, Third-party advisory
puppetlabs.comsecurity/cve/cve-2013-1640x_refsource_CONFIRM, Vendor advisory

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2013-1640"><img src="https://intel.neosec.eu/badge/cve/CVE-2013-1640.svg?lang=en" alt="CVE-2013-1640 – NEOSEC Intel" height="20"></a>