CVE-2009-5054: High severity smarty vulnerability

Published Feb 3, 2011
·
Updated

Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.

Affected Software

62 affected componentsFixes available
composer/smarty/smarty<3.0.0-beta4
3.0.0-beta4
Smarty smarty=1.4.3
Smarty smarty=1.0
Smarty smarty=1.0b
Smarty smarty=2.3.1
Smarty smarty=2.6.0-rc3
Smarty smarty=2.6.25
Smarty smarty=1.4.0
Smarty smarty=1.4.5
Smarty smarty=2.6.1
Smarty smarty=2.6.7
Smarty smarty=2.6.20
Smarty smarty=2.3.0
Smarty smarty=1.0a
Smarty smarty=1.1.0
Smarty smarty=1.4.0-b2
Smarty smarty=2.6.0
Smarty smarty=2.6.15
Smarty smarty=2.6.3
Smarty smarty=2.6.14
Smarty smarty=2.5.0-rc1
Smarty smarty=1.2.1
Smarty smarty=2.6.17
Smarty smarty=2.6.11
Smarty smarty=2.6.0-rc2
Smarty smarty=1.3.0
Smarty smarty=1.4.1
Smarty smarty=2.5.0-rc2
Smarty smarty=2.0.1
Smarty smarty=2.5.0
Smarty smarty=1.4.2
Smarty smarty=1.5.0
Smarty smarty=2.1.0
Smarty smarty<=2.6.26
Smarty smarty=2.6.22
Smarty smarty=1.5.2
Smarty smarty=2.6.12
Smarty smarty=2.6.18
Smarty smarty=1.5.1
Smarty smarty=2.0.0
Smarty smarty=2.4.1
Smarty smarty=2.6.6
Smarty smarty=2.6.16
Smarty smarty=2.6.9
Smarty smarty=1.2.2
Smarty smarty=2.6.0-rc1
Smarty smarty=2.6.24
Smarty smarty=2.1.1
Smarty smarty=2.6.4
Smarty smarty=2.2.0
Smarty smarty=2.4.2
Smarty smarty=2.6.10
Smarty smarty=2.6.2
Smarty smarty=1.4.0-b1
Smarty smarty=2.6.13
Smarty smarty=2.6.5
Smarty smarty=1.3.2
Smarty smarty=2.4.0
Smarty smarty=1.3.1
Smarty smarty=1.4.4
Smarty smarty=1.4.6
Smarty smarty=1.2.0

Event History

Feb 3, 2011
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
May 2, 2022
Advisory Published
via GitHub·04:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2009-5054?

CVE-2009-5054 has a moderate severity rating due to the potential for unauthorized file access.

2

How do I fix CVE-2009-5054?

To fix CVE-2009-5054, upgrade Smarty to version 3.0.0-beta4 or later.

3

Which versions of Smarty are affected by CVE-2009-5054?

CVE-2009-5054 affects Smarty versions prior to 3.0.0 beta 4.

4

What type of vulnerability is CVE-2009-5054?

CVE-2009-5054 is a file permission vulnerability that can lead to unintended access restrictions being bypassed.

5

Can I mitigate CVE-2009-5054 without upgrading?

Mitigating CVE-2009-5054 without upgrading is challenging; it's recommended to apply the upgrade for complete resolution.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203
CVE-2009-5054 - High severity smarty vulnerability - SecAlerts