First published: Thu Feb 03 2011(Updated: )
Smarty before 3.0.0, when security is enabled, does not prevent access to the (1) dynamic and (2) private object members of an assigned object, which has unspecified impact and remote attack vectors.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Smarty | =1.4.3 | |
Smarty | =1.0 | |
Smarty | =1.0b | |
Smarty | =2.3.1 | |
Smarty | =3.0.0-beta6 | |
Smarty | =2.6.0-rc3 | |
Smarty | =2.6.25 | |
Smarty | =3.0.0-beta8 | |
Smarty | =1.4.0 | |
Smarty | =1.4.5 | |
Smarty | =2.6.1 | |
Smarty | =2.6.7 | |
Smarty | =2.6.20 | |
Smarty | =2.3.0 | |
Smarty | =1.0a | |
Smarty | =1.1.0 | |
Smarty | <=3.0.0 | |
Smarty | =1.4.0-b2 | |
Smarty | =2.6.0 | |
Smarty | =2.6.15 | |
Smarty | =2.6.3 | |
Smarty | =3.0.0-rc2 | |
Smarty | =2.6.14 | |
Smarty | =2.5.0-rc1 | |
Smarty | =1.2.1 | |
Smarty | =2.6.17 | |
Smarty | =2.6.11 | |
Smarty | =2.6.0-rc2 | |
Smarty | =3.0.0-rc3 | |
Smarty | =3.0.0-beta7 | |
Smarty | =1.3.0 | |
Smarty | =1.4.1 | |
Smarty | =2.5.0-rc2 | |
Smarty | =2.0.1 | |
Smarty | =2.5.0 | |
Smarty | =1.4.2 | |
Smarty | =1.5.0 | |
Smarty | =2.1.0 | |
Smarty | =2.6.22 | |
Smarty | =1.5.2 | |
Smarty | =2.6.12 | |
Smarty | =2.6.18 | |
Smarty | =1.5.1 | |
Smarty | =2.0.0 | |
Smarty | =2.4.1 | |
Smarty | =2.6.6 | |
Smarty | =2.6.26 | |
Smarty | =2.6.16 | |
Smarty | =2.6.9 | |
Smarty | =1.2.2 | |
Smarty | =3.0.0-beta5 | |
Smarty | =2.6.0-rc1 | |
Smarty | =2.6.24 | |
Smarty | =2.1.1 | |
Smarty | =2.6.4 | |
Smarty | =2.2.0 | |
Smarty | =2.4.2 | |
Smarty | =2.6.10 | |
Smarty | =2.6.2 | |
Smarty | =1.4.0-b1 | |
Smarty | =2.6.13 | |
Smarty | =3.0.0-beta4 | |
Smarty | =2.6.5 | |
Smarty | =1.3.2 | |
Smarty | =2.4.0 | |
Smarty | =1.3.1 | |
Smarty | =1.4.4 | |
Smarty | =1.4.6 | |
Smarty | =1.2.0 | |
Smarty | =3.0.0-rc1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2010-4723 is categorized as medium due to its potential impact on security when improper access to object members occurs.
To fix CVE-2010-4723, upgrade Smarty to version 3.0.0 or later, where the vulnerability has been addressed.
CVE-2010-4723 affects Smarty versions prior to 3.0.0, including 1.0 through 2.6.26.
CVE-2010-4723 may allow unauthorized access to dynamic and private object members, posing risks of information disclosure.
Yes, CVE-2010-4723 can potentially be exploited through remote attack vectors.