CVE-2009-5054: Smarty Does Not Consider Umask Values When Setting Permissions

CVE-2009-5054 · Severity: info · Published 2022-05-02

Smarty Does Not Consider Umask Values When Setting Permissions

Technologies: smarty/smarty (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2009-5054 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2009-5054 being exploited in the wild.
How severe is CVE-2009-5054?
Informational severity, published 2 May 2022.
Which products and versions are affected?
smarty/smarty (Packagist) ECOSYSTEM:introduced=0,fixed=3.0.0-beta4.
Is there a fix for CVE-2009-5054?
Yes. smarty/smarty (Packagist): upgrade to 3.0.0-beta4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2009-5054?
Check whether you run smarty/smarty (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • smarty/smarty (Packagist): upgrade to 3.0.0-beta4 or later
    composer require smarty/smarty:^3.0.0-beta4

Affected products

  • smarty/smarty (Packagist) ECOSYSTEM:introduced=0,fixed=3.0.0-beta4

Identifiers

  • CVE-2009-5054
  • GHSA-6m9f-8vwq-97pm

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.