First published: Wed Jun 26 2013(Updated: )
A security flaw was found in the way Plone, a user friendly and powerful content management system, performed certain provided data validation when sending emails. A remote attacker, valid Plone user, could use this flaw to conduct email spoofing attacks.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/plone | >=4.3<4.3.2 | 4.3.2 |
pip/plone | >=4.2<4.2.6 | 4.2.6 |
pip/plone | >=2.1<=4.1 | 4.1.1 |
Plone CMS | =2.1 | |
Plone CMS | =2.1.1 | |
Plone CMS | =2.1.2 | |
Plone CMS | =2.1.3 | |
Plone CMS | =2.1.4 | |
Plone CMS | =2.5 | |
Plone CMS | =2.5.1 | |
Plone CMS | =2.5.2 | |
Plone CMS | =2.5.3 | |
Plone CMS | =2.5.4 | |
Plone CMS | =2.5.5 | |
Plone CMS | =3.0 | |
Plone CMS | =3.0.1 | |
Plone CMS | =3.0.2 | |
Plone CMS | =3.0.3 | |
Plone CMS | =3.0.4 | |
Plone CMS | =3.0.5 | |
Plone CMS | =3.0.6 | |
Plone CMS | =3.1 | |
Plone CMS | =3.1.1 | |
Plone CMS | =3.1.2 | |
Plone CMS | =3.1.3 | |
Plone CMS | =3.1.4 | |
Plone CMS | =3.1.5.1 | |
Plone CMS | =3.1.6 | |
Plone CMS | =3.1.7 | |
Plone CMS | =3.2 | |
Plone CMS | =3.2.1 | |
Plone CMS | =3.2.2 | |
Plone CMS | =3.2.3 | |
Plone CMS | =3.3 | |
Plone CMS | =3.3.1 | |
Plone CMS | =3.3.2 | |
Plone CMS | =3.3.3 | |
Plone CMS | =3.3.4 | |
Plone CMS | =3.3.5 | |
Plone CMS | =4.0 | |
Plone CMS | =4.0.1 | |
Plone CMS | =4.0.2 | |
Plone CMS | =4.0.3 | |
Plone CMS | =4.0.4 | |
Plone CMS | =4.0.5 | |
Plone CMS | =4.0.6.1 | |
Plone CMS | =4.1 | |
Plone CMS | =4.3 | |
Plone CMS | =4.3.1 | |
Plone CMS | =4.2 | |
Plone CMS | =4.2.1 | |
Plone CMS | =4.2.2 | |
Plone CMS | =4.2.3 | |
Plone CMS | =4.2.4 | |
Plone CMS | =4.2.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2013-4192 is considered medium due to the potential for email spoofing attacks by remote, authenticated attackers.
To fix CVE-2013-4192, upgrade Plone to version 4.3.2 or higher, or to version 4.2.6 or higher.
CVE-2013-4192 affects Plone versions from 2.1 through 4.1, as well as certain 4.2.x versions prior to 4.2.6.
Yes, CVE-2013-4192 can be exploited remotely by a valid Plone user to conduct email spoofing.
Yes, a hotfix is available for CVE-2013-4192 that addresses the data validation flaw.