First published: Wed Mar 30 2011(Updated: )
Nicolas Grégoire discovered that xmlsec1 can create a file with attacker-specified path name and content when xmlsec1 is used to verify a signature of a specially-crafted XML file specifying XSLT transformation. This may be used to create or overwrite arbitrary file writeable to the user running xmlsec1. This issue was addressed upstream via following commit, which disables XSLT read/write by default: <a href="http://git.gnome.org/browse/xmlsec/commit/?id=35eaacde6093d6711339754fc2146341b8b9f5fa">http://git.gnome.org/browse/xmlsec/commit/?id=35eaacde6093d6711339754fc2146341b8b9f5fa</a> Acknowledgements: Red Hat would like to thank Nicolas Grégoire and Aleksey Sanin for reporting this issue.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/xmlsec1 | <1.2.17 | 1.2.17 |
Aleksey XML Security Library | <=1.2.16 | |
Aleksey XML Security Library | =0.0.3 | |
Aleksey XML Security Library | =1.2.10 | |
Aleksey XML Security Library | =0.0.2a | |
Aleksey XML Security Library | =0.0.5 | |
Aleksey XML Security Library | =0.0.9 | |
Aleksey XML Security Library | =1.2.13 | |
Aleksey XML Security Library | =1.2.9 | |
Aleksey XML Security Library | =1.2.14 | |
Aleksey XML Security Library | =1.0.3 | |
Aleksey XML Security Library | =1.2.8 | |
Aleksey XML Security Library | =0.0.13 | |
Aleksey XML Security Library | =0.1.1 | |
Aleksey XML Security Library | =1.0.2 | |
Aleksey XML Security Library | =0.0.2 | |
Aleksey XML Security Library | =1.2.2 | |
Aleksey XML Security Library | =1.1.1 | |
Aleksey XML Security Library | =1.0.0-rc1 | |
Aleksey XML Security Library | =0.0.12 | |
Aleksey XML Security Library | =0.0.14 | |
Aleksey XML Security Library | =0.0.10 | |
Aleksey XML Security Library | =1.2.4 | |
Aleksey XML Security Library | =1.0.1 | |
Aleksey XML Security Library | =0.0.7 | |
Aleksey XML Security Library | =0.0.6 | |
Aleksey XML Security Library | =1.2.1 | |
Aleksey XML Security Library | =1.2.7 | |
Aleksey XML Security Library | =0.0.15 | |
Aleksey XML Security Library | =1.2.11 | |
Aleksey XML Security Library | =1.0.4 | |
Aleksey XML Security Library | =1.2.5 | |
Aleksey XML Security Library | =1.1.0 | |
Aleksey XML Security Library | =1.2.3 | |
Aleksey XML Security Library | =1.1.2 | |
Aleksey XML Security Library | =1.2.6 | |
Aleksey XML Security Library | =0.1.0 | |
Aleksey XML Security Library | =1.2.15 | |
Aleksey XML Security Library | =1.2.0 | |
Aleksey XML Security Library | =1.0.0 | |
Aleksey XML Security Library | =0.0.11 | |
Aleksey XML Security Library | =0.0.4 | |
Apple WebKit | ||
Aleksey XML Security Library | =0.0.1 | |
Aleksey XML Security Library | =0.0.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-1425 is considered a high severity vulnerability due to its potential for arbitrary file overwrite.
To fix CVE-2011-1425, upgrade to xmlsec1 version 1.2.17 or later.
CVE-2011-1425 affects xmlsec1 versions prior to 1.2.17 and various versions of the Aleksey XML Security Library.
Yes, CVE-2011-1425 can potentially be exploited remotely through specially-crafted XML files.
Exploitation of CVE-2011-1425 may lead to unauthorized file creation or modification on the affected system.